Dedicated Server

                                                         

                                   MANAGED ROOT SERVER

    Managed Root Server

A root server is a piece of the supporting foundation of the Internet, and encourages Internet use by going about as the foundation of online access. Root servers are a fundamental piece of the area name framework (DNS). They distribute root zone document substance, which are in charge of DNS usefulness, to the Internet.

Root Server

A name server is a computer application that implements a network service for providing responses to queries against a directory service. It translates an often humanly meaningful, text-based identifier to a system-internal, often numeric identification or addressing component. This service is performed by the server in response to a service protocol request.

An example of a name server is the server component of the Domain Name System (DNS), one of the two principal namespaces of the Internet. The most important function of DNS servers is the translation (resolution) of human-memorable domain names and hostnames into the corresponding numeric Internet Protocol (IP) addresses, the second principal name space of the Internet which is used to identify and locate computer systems and resources on the Internet.

Contents
1

• Domain Name Server
  • 1.1Authoritative name server
  • 1.2Authoritative answer
  • 1.3Recursive query
  • 1.4Caching name server
• 2See also
• 3References
• 4External links

Area Name Server 
Fundamental article: Domain Name System 
The Internet keeps up two important namespaces: the area name hierarchy[1] and the IP address system.[2] The Domain Name System keeps up the space namespace and gives interpretation benefits between these two namespaces. Web name servers actualize the Domain Name System.[3] The top chain of importance of the Domain Name System is served by the root name servers kept up by appointment by the Internet Corporation for Assigned Names and Numbers (ICANN). Underneath the root, Internet assets are sorted out into a chain of importance of spaces, directed by the individual enlistment centers and area name holders. A DNS name server is a server that stores the DNS records, for example, address (An, AAAA) records, name server (NS) records, and mail exchanger (MX) records for a space name (see additionally List of DNS record types) and reacts with answers to inquiries against its database.
Legitimate name server 
A legitimate name server is a name server that gives responds to because of inquiries got some information about names in a zone. A definitive just name server returns answers just to questions about area names that have been explicitly designed by the manager. Name servers can likewise be arranged to give definitive responses to questions in certain zones, while going about as a storing name server for all other zones.[4]
Definitive Name Server
A definitive name server can either be an essential server (ace) or an optional server (slave). An essential server for a zone is the server that stores the conclusive adaptations of all records in that zone. It is distinguished by beginning of-expert (SOA) asset record. An auxiliary server for a zone utilizes a programmed refreshing instrument to keep up an indistinguishable duplicate of the essential server's database for a zone. Instances of such instruments incorporate DNS zone exchanges and record exchange conventions. DNS gives a system whereby the essential for a zone can advise all the known secondaries for that zone when the substance of the zone have changed. The substance of a zone are either physically arranged by a director, or oversaw utilizing Dynamic DNS.[5]
Each space name shows up in a zone served by at least one legitimate name servers. The completely qualified area names of the definitive name servers of a zone are recorded in the NS records of that zone. In the event that the server for a zone isn't likewise definitive for its parent zone, the server for the parent zone must be arranged with an appointment for the zone.[6]
At the point when an area is enrolled with a space name enlistment center, the zone manager gives the rundown of name servers (commonly no less than two, for redundancy[7]) that are definitive for the zone that contains the area. The enlistment center gives the names of these servers to the area library for the top dimension space containing the zone. The area library thus designs the legitimate name servers for that top dimension space with appointments for every server for the zone. On the off chance that the completely qualified space name of any name server for a zone shows up inside that zone, the zone manager gives IP delivers to that name server, which are introduced in the parent zone as paste records; generally, the appointment comprises of the rundown of NS records for that zone.[8]
Definitive answer 
A name server demonstrates that its reaction is definitive by setting the Authoritative Answer (AA) bit in the reaction to an inquiry on a name for which it is legitimate. Name servers giving responses to which they are not legitimate (for instance, name servers for parent zones) don't set the AA bit.[3]
Recursive inquiry
In the event that a name server can't answer an inquiry since it doesn't contain a passage for the host in its DNS reserve, it might recursively question name servers higher up in the hierarchy.[9]This is known as a recursive question or recursive query. A server giving recursive inquiries is known as a recursive name server or recursive DNS, once in a while shortened as recdns.[10]
On a fundamental level, legitimate name servers get the job done for the activity of the Internet. In any case, with just legitimate name-servers working, each DNS inquiry must begin with recursive inquiries at the root zone of the Domain Name System and every client framework must actualize resolver programming fit for recursive operation.[clarification needed]
Reserving name server
Reserving name servers (DNS stores) store DNS question results for a timeframe decided in the design (time-to-live) of every area name record. DNS reserves improve the proficiency of the DNS by decreasing DNS traffic over the Internet, and by lessening load on definitive name-servers, especially root name-servers. Since they can respond to questions all the more rapidly, they likewise increment the execution of end-client applications that utilization the DNS. Recursive name servers settle any inquiry they get, regardless of whether they are not legitimate for the inquiry being asked, by counseling the server or servers that are definitive for the inquiry. Reserving name servers are frequently additionally recursive name servers—they play out each progression important to answer any DNS question they get. To do this the name server questions each legitimate name-server thusly, beginning from the DNS root zone. It proceeds until it achieves the definitive server for the zone that contains the questioned area name. That server gives the response to the inquiry, or conclusively says it can't be replied, and the storing resolver then returns this reaction to the customer that made the inquiry. The specialist, settling and reserving capacities would all be able to be available in a DNS server execution, yet this isn't required: a DNS server can actualize any of these capacities alone, without executing the others. Web access suppliers commonly give reserving resolvers to their clients. Moreover, many home-systems administration switches actualize storing resolvers to improve productivity in the nearby system. A few frameworks use nscd - the name administration reserving daemon[11]
Open Root Server Network
From Wikipedia, the free encyclopediaJump to navigationJump to searchOpen Root Server Network logo

• ICANN BASED (default) operating mode involves daily synchronization, except that removed TLDs are not removed from the ORSN root.

• INDEPENDENT mode has no automatic synchronization and is activated "whenever the political situation of the world - in our opinion - makes this step necessary because the possibility of a modification and/or a downtime of the ICANN root zone exists or we do not want that our root zone will rebuild automatically."^[5]

Open Root Server Network (ORSN) is a network of Domain Name System root nameservers for the Internet. ORSN DNS root zoneinformation is normally kept in synchronization with the "official" Domain Name System root nameservers coordinated by ICANN. The networks are thus 100% compatible, though ORSN is operated independently. The ORSN servers are primarily placed in Europe. ORSN is also used by public name servers, providing Domain Name System access freely for everyone, without any limitation.

ORSN was primarily started to reduce the over-dependence of Internet users on the United States and Department of Commerce/IANA/ICANN/VeriSign, limit the control over the Internet that this gives, while ensuring that domain names remain unambiguous. And to avoid the technical possibility of global "Internet shutdown" by one party.^[1] They also expect their network to make domain name resolutions faster for everyone.

Markus Grundmann, Germany is the founder of ORSN, and author of ORSN distributed system management and monitoring software solution.

Paul Vixie, the main designer of BIND, the UNIX de facto standard DNS server, is a high-profile proponent of the ORSN.^[2] Paul Vixie is member of Security and Stability Advisory Committee of ICANN,^[3] he served on the Board of Trustees of the American Registry for Internet Numbers (ARIN) from 2005 to 2013, also as ARIN chairman in 2009 and 2010.^[

ORSN has 2 operating modes:

ORSN operated from February 2002 until the end of 2008.^[6] ORSN operates again since June 2013.^[7] Several Internet service providers in Europe used ORSN as a root for their name servers.

The Internet Corporation for Assigned Names and Numbers (ICANN /ˈaɪkæn/ EYE-kan) is a nonprofit organization responsible for coordinating the maintenance and procedures of several databases related to the namespaces and numerical spaces of the Internet, ensuring the network's stable and secure operation.^[1] ICANN performs the actual technical maintenance work of the Central Internet Address pools and DNS root zone registries pursuant to the Internet Assigned Numbers Authority (IANA) function contract. The contract regarding the IANA stewardship functions between ICANN and the National Telecommunications and Information Administration (NTIA) of the United States Department of Commerce ended on October 1, 2016, formally transitioning the functions to the global multistakeholder community.^[2][3][4][5]

Much of its work has concerned the Internet's global Domain Name System (DNS), including policy development for internationalization of the DNS system, introduction of new generic top-level domains (TLDs), and the operation of root name servers. The numbering facilities ICANN manages include the Internet Protocol address spaces for IPv4 and IPv6, and assignment of address blocks to regional Internet registries. ICANN also maintains registries of Internet Protocol identifiers.

ICANN's primary principles of operation have been described as helping preserve the operational stability of the Internet; to promote competition; to achieve broad representation of the global Internet community; and to develop policies appropriate to its mission through bottom-up, consensus-based processes.^[6]

ICANN's creation was announced publicly on September 17, 1998,^[7] and it formally came into being on September 30, 1998, incorporated in the U.S. state of California.^[8] Originally headquartered in Marina del Rey in the same building as the University of Southern California's Information Sciences Institute (ISI), its offices are now in the Playa Vista neighborhood of Los Angeles.

Contents

• 1History
• 2Notable events
• 3Structure
  • 3.1Governmental Advisory Committee
    • 3.1.1Representatives
    • 3.1.2Observers
    • 3.1.3Key holders
  • 3.2Democratic input
• 4Activities
  • 4.1Uniform Domain-Name Dispute Resolution Policy (UDRP)
  • 4.2Proposed elimination of public DNS whois
• 5Criticism
  • 5.1IBSA proposal (2011)
  • 5.2Montevideo Statement on the Future of Internet Cooperation (2013)
  • 5.3Global Multistakeholder Meeting on the Future of Internet Governance (2013)
  • 5.4NetMundial Initiative (2014)
  • 5.5.sucks domain
    • 5.5.1Controversy
  • 5.6.islam and .halal domains
• 6See also
• 7References
• 8Further reading
• 9External links

ICANN

Before the establishment of ICANN, the IANA function of administering registries of Internet protocol identifiers (including the distributing top-level domains and IP addresses) was performed by Jon Postel, a Computer Science researcher who had been involved in the creation of ARPANET, first at UCLA and then at USC-ISI.^[9][10] In 1997 Postel testified before Congress that this had come about as a "side task" to this research work.^[11] The Information Sciences Institute was funded by the U.S. Department of Defense, as was SRI International's Network Information Center, which also performed some assigned name functions.^[12]

As the Internet grew and expanded globally, the U.S. Department of Commerce initiated a process to establish a new organization to perform the IANA functions. On January 30, 1998, the National Telecommunications and Information Administration (NTIA), an agency of the U.S. Department of Commerce, issued for comment, "A Proposal to Improve the Technical Management of Internet Names and Addresses." The proposed rule making, or "Green Paper",^[13] was published in the Federal Register on February 20, 1998, providing opportunity for public comment. NTIA received more than 650 comments as of March 23, 1998, when the comment period closed.^[14]

The Green Paper proposed certain actions designed to privatize the management of Internet names and addresses in a manner that allows for the development of competition and facilitates global participation in Internet management. The Green Paper proposed for discussion a variety of issues relating to DNS management including private sector creation of a new not-for-profit corporation (the "new corporation") managed by a globally and functionally representative board of directors.^[15] ICANN was formed in response to this policy.^{[citation needed]} ICANN managed the Internet Assigned Numbers Authority (IANA) under contract to the United States Department of Commerce (DOC) and pursuant to an agreement with the IETF.^[16]

ICANN was incorporated in California on September 30, 1998, with entrepreneur and philanthropist Esther Dyson as founding chairwoman.^[8] It is a nonprofit public benefit corporation "organized under the California Nonprofit Public Benefit Corporation Law for charitable and public purposes."^[17] ICANN was established in California due to the presence of Jon Postel, who was a founder of ICANN and was set to be its first Chief Technology Officer prior to his unexpected death. ICANN formerly operated from the same Marina del Rey building where Postel formerly worked, which is home to an office of the Information Sciences Institute at the University of Southern California. However, ICANN's headquarters is now located in the nearby Playa Vista neighborhood of Los Angeles.

Per its original by-laws,^[18] primary responsibility for policy formation in ICANN was to be delegated to three supporting organizations (Address Supporting Organization, Domain Name Supporting Organization, and Protocol Supporting Organization), each of which was to develop and recommend substantive policies and procedures for the management of the identifiers within their respective scope. They were also required to be financially independent from ICANN.^[19] As expected, the Regional Internet Registries and the IETF agreed to serve as the Address Supporting Organization and Protocol Supporting Organization respectively,^[20][21] and ICANN issued a call for interested parties to propose the structure and composition of the Domain Name Supporting Organization.^[22] In March 1999, the ICANN Board, based in part on the DNSO proposals received, decided instead on an alternate construction for the DNSO which delineated specific constituencies bodies within ICANN itself,^[23][24] thus adding primary responsibility for DNS policy development to ICANN's existing duties of oversight and coordination.