Root nameserver

A root name server is a DNS server that answers requests for the DNS root zone, and redirects requests for a particular top-level domain (TLD) to that TLD's nameservers. 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 namespace domain for the Internet's official global implementation of the Domain Name System.

All domain names on the Internet can be regarded as ending in a full stop character e.g. "www.example.com.". This final dot is generally implied rather than explicit, as modern DNS software does not actually require that the final dot be included when attempting to translate a domain name to an IP address. The empty string after the final dot is called the root domain, and all other domains (.com, .org, .net, and so on) are contained within the root domain.

When a computer on the Internet wants to resolve a domain name, it works from right to left, asking each name server in turn about the element to its left. The root name servers (which have responsibility for the . domain) know which servers are responsible for the top-level domains. Each top-level domain (such as .com) has its own set of servers, which in turn delegate to the name servers responsible for individual domain names (such as example.com), which in turn answer queries for IP addresses of subdomains or hosts (such as www).

In practice, most of this information does not change very often and gets cached, and "necessary" DNS lookups to the root nameservers are relatively rare. A survey from 2003 [cite web
coauthors = Duane Wessels, Marina Fomenkov
title = Wow, That’s a Lot of Packets
date = 2003
url = http://dns.measurement-factory.com/writings/wessels-pam2003-paper.pdf
format = PDF
accessdate = 2008-02-05] found 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, which is incorrect. A similar list of observed problems and recommended fixes can be found in RFC 4697.

There are currently 13 root name servers specified, with names in the form "letter".root-servers.net, where "letter" ranges from A to M. (Seven of these are not actual single servers, but represent several physical servers each in multiple geographical locations; cf. below.):

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

No more names are added because of limitations in the original DNS specification, which specifies a maximum packet size of 512 bytes using the User Datagram Protocol(UDP). [RFC 1035 Domain names - implementation and specification] This restriction existed because the minimum IP packet size that was required to be transmitted without fragmentation was 576 bytes. The DNS priming exchange is getting close to 512 bytes. [ [http://www.icann.org/committees/security/sac018.pdf ICANN: Accommodating IP Version 6 Address Resource Records for the Root of the Domain Name System] ] However, the C, F, 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, rather than nominal, root servers are now outside the United States.

There are also quite a few alternative namespace systems with their own set of root nameservers that exist in opposition to the mainstream nameservers. The first, AlterNIC, generated a substantial amount of press. See Alternative DNS root for more information.

Root name servers may also be run locally, on provider or other types of networks, synchronized with the US Department of Commerce delegated root zone file [http://www.internic.net/zones/root.zone as published] by ICANN. Such a server is not an alternative root, but a local implementation of A through M.

As the root nameservers function as 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 hamper the performance of the Internet.

ee also

* Anycast
* DNS Backbone DDoS Attacks
* EDNS0 (Extended DNS, version 0)
* Domain Name System
* Internet backbone
* Open Root Server Network
* blackhole server

References

* [http://www.root-servers.org/ Root Server Technical Operations Association]
* [http://www.circleid.com/posts/dns_root_servers_google_maps/ Root Servers' Geographical Locations on Google Maps]
* [http://www.rssac.org/ DNS Root Server System Advisory Committee]
* [http://www.isoc.org/briefings/019/ DNS Root Name Servers Explained For Non-Experts]
* [http://www.isoc.org/briefings/020/ DNS Root Name Servers Frequently Asked Questions]
* [http://www.apnic.net/services/rootserver/ Location of Root servers in Asia-Pacific]
* [http://www.bind9.net/dnshealth/ Bogus Queries received at the Root Servers]
* [http://www.orsn.org/ ORSN, Open Root Server Network with IPv6 support in europe]
* RFC 2826 - IAB Technical Comment on the Unique DNS Root
* RFC 2870 - Root Name Server Operational Requirements
* RFC 4697 - Observed DNS Resolution Misbehavior (from observations on the Root Servers)

External links

* [http://www.root-servers.org/ Root Server Technical Operations Association]
* ftp://ftp.internic.net/domain/
* http://private.dnsstuff.com/info/roottimes.htm Root Server response times