Root name server

From Wikipedia, the free encyclopedia
  (Redirected from Root servers)
Jump to: navigation, search
A Cisco 7301 router and a Juniper M7i, part of the K root-server instance at AMS-IX.

A root name server is a name server for the root zone of the Domain Name System of the Internet. It directly answers requests for records in the root zone and answers other requests by returning a list of the authoritative name servers for the appropriate top-level domain (TLD). The root name servers are a critical part of the Internet infrastructure because they are the first step in translating (resolving) human readable host names into IP addresses that are used in communication between Internet hosts.

A combination of limits in the DNS and certain protocols, namely the practical size of unfragmented User Datagram Protocol (UDP) packets, resulted in a decision to limit the number of root servers to thirteen server addresses. The use of anycast addressing permits the actual number of root server instances to be much larger, and is 386 as of 25 January 2014.[1]

Root domain[edit]

The Domain Name System is a hierarchical naming system for computers, services, or any resource participating in the Internet. The top of that hierarchy is the root domain. The root domain does not have a formal name and its label in the DNS hierarchy is an empty string. All fully qualified domain names (FQDNs) on the Internet can be regarded as ending with this empty string for the root domain, and therefore ending in a full stop character (the label delimiter), e.g., www.example.com.. This is generally implied rather than explicit, as modern DNS software does not actually require that the terminating dot be included when attempting to translate a domain name to an IP address.

The root domain contains all top-level domains of the Internet. As of June 2009, it contains 20 generic top-level domains (gTLDs) and 248 country code top-level domains (ccTLDs) in the root domain.[2] In addition, the ARPA domain is used for technical name spaces in the management of Internet addressing and other resources. A TEST domain is used for testing internationalized domain names.

Resolver operation[edit]

When a computer on the Internet needs to resolve a domain name, it uses resolver software to perform the lookup. A resolver breaks the name up into its labels from right to left. The first component (TLD) is queried using a root server to obtain the responsible authoritative server. Queries for each label return more specific name servers until a name server returns the answer of the original query.

In practice, most of this information does not change very often over a period of hours and therefore it is cached by intermediate name servers or by a name cache built into the user's application. DNS lookups to the root name servers may therefore be relatively infrequent. A survey in 2003 [3] reports that only 2% of all queries to the root servers were legitimate. Incorrect or non-existent caching was responsible for 75% of the queries, 12.5% were for unknown TLDs, 7% were for lookups using IP addresses as if they were domain names, etc. Some misconfigured desktop computers even tried to update the root server records for the TLDs. A similar list of observed problems and recommended fixes has been published in RFC 4697.

Although any local implementation of DNS can implement its own private root name servers, the term "root name server" is generally used to describe the thirteen well-known root name servers that implement the root name space domain for the Internet's official global implementation of the Domain Name System.

Root server addresses[edit]

As of February 2013, there are 13 root name servers specified, with names in the form letter.root-servers.net, where letter ranges from A to M. This does not mean there are 13 physical servers; each operator uses redundant computer equipment to provide reliable service even if failure of hardware or software occurs. Additionally, nine of the servers operate in multiple geographical locations using a routing technique called anycast addressing, providing increased performance and even more fault tolerance.

Ten servers were originally in the United States; some are now operated using anycast addressing. Three servers were originally located in Stockholm (I), Amsterdam (K), and Tokyo (M).

Letter IPv4 address IPv6 address AS-number[4] Old name Operator Location
#sites (global/local)[5]
Software
A 198.41.0.4 2001:503:ba3e::2:30 AS19836,[4][note 1] AS36619, AS36620, AS36622, AS36625, AS36631, AS64820[note 2][6] ns.internic.net Verisign Distributed using anycast
4/0
BIND
B 192.228.79.201[note 3][7] 2001:478:65::53 (none),[4] AS4[8] ns1.isi.edu USC-ISI Marina Del Rey, California, U.S.
0/1
BIND
C 192.33.4.12 2001:500:2::c AS2149[4][9] c.psi.net Cogent Communications Distributed using anycast
8/0
BIND
D 199.7.91.13[note 4][10] 2001:500:2d::d AS27[4][11] terp.umd.edu University of Maryland Distributed using anycast
8/3
BIND
E 192.203.230.10 N/A AS297,[4][12][13] AS42[12] ns.nasa.gov NASA Distributed using anycast
1/11
BIND
F 192.5.5.241 2001:500:2f::f AS3557,[4][14] AS1280, AS30132[14] ns.isc.org Internet Systems Consortium Distributed using anycast
5/51
BIND 9[15]
G 192.112.36.4 N/A AS5927[4][16] ns.nic.ddn.mil Defense Information Systems Agency Distributed using anycast
6/0
BIND
H 128.63.2.53 2001:500:1::803f:235 AS13[4][17] aos.arl.army.mil U.S. Army Research Lab Aberdeen Proving Ground, Maryland, U.S., San Diego, California, U.S.
2/0
NSD
I 192.36.148.17 2001:7fe::53 AS29216[4][18] nic.nordu.net Netnod Distributed using anycast
0/43[note 5]
BIND
J 192.58.128.30[note 6] 2001:503:c27::2:30 AS26415,[4][19] AS36626, AS36628, AS36632[19] Verisign Distributed using anycast
61/13
BIND
K 193.0.14.129 2001:7fd::1 AS25152[4][20][21] RIPE NCC Distributed using anycast
5/12
NSD[22]
L 199.7.83.42[note 7][23] 2001:500:3::42 AS20144[4][24][25] ICANN Distributed using anycast
0/146[note 5]
NSD[26]
M 202.12.27.33 2001:dc3::35 AS7500[4][27][28] WIDE Project Distributed using anycast
5/1
BIND

Older servers had their own name before the policy of using similar names was established.

The choice of thirteen name servers was made because of limitations in the original DNS specification,[why?] which specifies a maximum packet size of 512 bytes when using the User Datagram Protocol (UDP).[29] Technically however, fourteen name servers fit into an IPv4 packet. The addition of IPv6 addresses for the root name servers requires more than 512 bytes, which is facilitated by the EDNS0 extension to the DNS standard.[30] While only thirteen names are used for the root name servers, there are many more physical servers; A, C, E, F, G, I, J, K, L and M servers now exist in multiple locations on different continents, using anycast address announcements to provide decentralized service. As a result most of the physical root servers are now outside the United States, allowing for high performance worldwide.

A map of the thirteen logical name servers, including anycasted instances, at the end of 2006.

There are also several alternative namespace systems with an alternative DNS root using their own set of root name servers that exist in parallel to the mainstream name servers. The first, AlterNIC, generated a substantial amount of press.[citation needed]

The function of a root name server may also be implemented locally, or on a provider network. Such servers are synchronized with the official root zone file as published by ICANN, and do not constitute an alternate root.

As the root name servers are an important part of the Internet, they have come under attack several times, although none of the attacks have ever been serious enough to severely affect the performance of the Internet.

Root server supervision[edit]

The DNS Root Server System Advisory Committee is an ICANN committee. However, the root zone is controlled by the United States Department of Commerce who must approve all changes to the root zone file requested by ICANN. ICANN's bylaws[31] assign authority over the operation of the root name servers of the Domain Name System to the DNS Root Server System Advisory Committee.

Root zone file[edit]

The root zone file is a small (about 550 kB) data set[32] whose publication is the primary purpose of root name servers.

The root zone file is at the apex of a hierarchical distributed database called the Domain Name System (DNS). This database is used by almost all Internet applications to translate worldwide unique names like www.wikipedia.org into other identifiers such as IP addresses.

The contents of the root zone file is a list of names and numeric IP addresses of the authoritative DNS servers for all top-level domains (TLDs) such as com, org, edu, or the country code top-level domains. On 12 December 2004, there were 258 TLDs and 773 different authoritative servers for those TLDs listed. Other name servers forward queries for which they do not have any information about authoritative servers to a root name server. The root name server, using its root zone file, answers with a referral to the authoritative servers for the appropriate TLD or with an indication that no such TLD exists.[33]

See also[edit]

Notes[edit]

  1. ^ AS19836 is not listed by the RIPEstat tool
  2. ^ AS64820 is listed as "private use" in RIPE's RISwhois tool
  3. ^ (since January 2004; originally was 128.9.0.107)
  4. ^ (since January 3, 2013; originally was 128.8.10.90)
  5. ^ a b These sites are not bold in the source, which says: "bold indicates global sites".
  6. ^ (since November 2002; originally was 198.41.0.10)
  7. ^ (since November 2007; originally was 198.32.64.12)

References[edit]

  1. ^ "www.root-servers.org". Retrieved 2014-01-25. 
  2. ^ "List of top-level domains". ICANN. 
  3. ^ Duane Wessels, Marina Fomenkov (2003). "Wow, That’s a Lot of Packets" (PDF). Retrieved 2013-11-07. 
  4. ^ a b c d e f g h i j k l m n AS-numbers and IP-addresses from Root-servers.org homepage checked 9 January 2014
  5. ^ Location and sites from Root-servers.org homepage checked 9 January 2014
  6. ^ "RIS — RIPE Network Coordination Centre". Ris.ripe.net. Retrieved 2014-01-23. 
  7. ^ "New IPv4 address for b.root-servers.net". 
  8. ^ "RIS — RIPE Network Coordination Centre". Ris.ripe.net. 2013-08-20. Retrieved 2014-01-23. 
  9. ^ "RIS — RIPE Network Coordination Centre". Ris.ripe.net. 2013-10-13. Retrieved 2014-01-23. 
  10. ^ "D-Root is Changing its IPv4 Address on 3 January 2013". 
  11. ^ RISwhois, excluding less-specific AS3303 route announcement
  12. ^ a b "RIS — RIPE Network Coordination Centre". Ris.ripe.net. Retrieved 2014-01-23. 
  13. ^ "Peering Networks Detailed View". Peeringdb.com. 2013-03-11. Retrieved 2014-01-23. 
  14. ^ a b "RIS — RIPE Network Coordination Centre". Ris.ripe.net. Retrieved 2014-01-23. 
  15. ^ F-root | Internet Systems Consortium
  16. ^ "RIS — RIPE Network Coordination Centre". Ris.ripe.net. 2013-09-18. Retrieved 2014-01-23. 
  17. ^ "RIS — RIPE Network Coordination Centre". Ris.ripe.net. 2014-01-02. Retrieved 2014-01-23. 
  18. ^ "RIS — RIPE Network Coordination Centre". Ris.ripe.net. Retrieved 2014-01-23. 
  19. ^ a b "RIS — RIPE Network Coordination Centre". Ris.ripe.net. Retrieved 2014-01-23. 
  20. ^ "RIS — RIPE Network Coordination Centre". Ris.ripe.net. 2013-06-20. Retrieved 2014-01-23. 
  21. ^ "Peering Networks Detailed View". Peeringdb.com. 2013-10-21. Retrieved 2014-01-23. 
  22. ^ K-root Homepage
  23. ^ "Advisory — "L Root" changing IP address on 1st November". ICANN. 
  24. ^ [1], excluding less-specific AS3303 route announcement
  25. ^ "Peering Networks Detailed View". Peeringdb.com. 2013-04-15. Retrieved 2014-01-23. 
  26. ^ l.root-servers.net
  27. ^ "RIS — RIPE Network Coordination Centre". Ris.ripe.net. 2013-10-21. Retrieved 2014-01-23. 
  28. ^ "Peering Networks Detailed View". Peeringdb.com. 2013-12-23. Retrieved 2014-01-23. 
  29. ^ RFC 1035 Domain names - implementation and specification
  30. ^ ICANN: Accommodating IP Version 6 Address Resource Records for the Root of the Domain Name System
  31. ^ ICANN Bylaws XI-2.3
  32. ^ IANA: Root Files
  33. ^ ISOC, DNS Root Name Servers explained for the non-expert, (Available online, accessed 19 March 2010.)

Further reading[edit]

External links[edit]