Root Nameserver explained
A root name server is a DNS server that answers requests for the root namespace domain, 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.web-hosting-top.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 (i.e. .com, .org, .net, etc.) 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 about which servers are responsible for the top-level domains. Each top-level domain (such as .org) has its own set of servers, which in turn delegate to the name servers responsible for individual domain names (such as web-hosting-top.com), which in turn answer queries for IP addresses of subdomains or hosts (such as www).
In practice, most of this information doesn't change very often and gets cached, and necessary DNS lookups to the root nameservers are relatively rare. However, there are many incorrectly configured systems on the Internet that are responsible for the majority of root nameserver lookup traffic. For example, queries with the source address 0.0.0.0 (corresponding to anywhere and everywhere) make it to the root servers. Also, misconfigured desktop computers sometimes try to update the root server records for the TLDs, which is incorrect.
There are currently 13 root name servers specified, with names in the form letter.root-servers.net, where letter ranges from A to M. (Six 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 can be used because of protocol limitations - UDP packet can only carry 512 bytes reliably and a hint file with more than 13 servers would be larger than 512 bytes - but the C, F, I, J, K and M servers now exist in multiple locations on different continents, using anycast announcements to provide a 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 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 part of the Internet backbone, 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.
All domain names on the Internet can be regarded as ending in a full stop character e.g. "www.web-hosting-top.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 (i.e. .com, .org, .net, etc.) 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 about which servers are responsible for the top-level domains. Each top-level domain (such as .org) has its own set of servers, which in turn delegate to the name servers responsible for individual domain names (such as web-hosting-top.com), which in turn answer queries for IP addresses of subdomains or hosts (such as www).
In practice, most of this information doesn't change very often and gets cached, and necessary DNS lookups to the root nameservers are relatively rare. However, there are many incorrectly configured systems on the Internet that are responsible for the majority of root nameserver lookup traffic. For example, queries with the source address 0.0.0.0 (corresponding to anywhere and everywhere) make it to the root servers. Also, misconfigured desktop computers sometimes try to update the root server records for the TLDs, which is incorrect.
There are currently 13 root name servers specified, with names in the form letter.root-servers.net, where letter ranges from A to M. (Six of these are not actual single servers, but represent several physical servers each in multiple geographical locations; cf. below.):
Letter | IP address | Old name | Operator | Location | Software |
---|---|---|---|---|---|
A | 198.41.0.4 | ns.internic.net | VeriSign | Dulles, Virginia, U.S. | BIND |
B | 192.228.79.201 | ns1.isi.edu | USC-ISI | Marina Del Rey, California, U.S. | BIND |
C | 192.33.4.12 | c.psi.net | Cogent Communications | distributed using anycast | BIND |
D | 128.8.10.90 | terp.umd.edu | University of Maryland | College Park, Maryland, U.S. | BIND |
E | 192.203.230.10 | ns.nasa.gov | NASA | Mountain View, California, U.S. | BIND |
F | 192.5.5.241 | ns.isc.org | ISC | distributed using anycast | BIND |
G | 192.112.36.4 | ns.nic.ddn.mil | Defense Information Systems Agency | Columbus, Ohio, U.S. | BIND |
H | 128.63.2.53 | aos.arl.army.mil | U.S. Army Research Lab | Aberdeen Proving Ground, Maryland, U.S. | NSD |
I | 192.36.148.17 | nic.nordu.net | Autonomica | distributed using anycast | BIND |
J | 192.58.128.30 | VeriSign | distributed using anycast | BIND | |
K | 193.0.14.129 | RIPE NCC | distributed using anycast | NSD | |
L | 198.32.64.12 | ICANN | Los Angeles, California, U.S. | NSD | |
M | 202.12.27.33 | WIDE Project | distributed using anycast | BIND |
Older servers had their own name before the policy of using similar names was established.
No more names can be used because of protocol limitations - UDP packet can only carry 512 bytes reliably and a hint file with more than 13 servers would be larger than 512 bytes - but the C, F, I, J, K and M servers now exist in multiple locations on different continents, using anycast announcements to provide a 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 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 part of the Internet backbone, 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.
📣 Latest tweets mentioning Root Nameserver
MaxRDP 🏆 Alexa 363,515▲ - 📅 - Looking For Best windows RDP with root access ? see our plans of windows Private RDP . #privaterdp #windowsvps… more info
Instant SSL 🏆 Alexa 532,609▲ - 📅 - @RootCausesPod In 2022 Mozilla added a root program requirement that CAs include Reason Codes when revoking public… more info
Floki NET 🏆 Alexa 329,533▼ - 📅 - ️High-performance dedicated server with robust, free DDoS protection, root access, and enterprise-grade hardware.… more info
Host Gator India 🏆 Alexa 13,731▲ - 📅 - Give your business idea the platform it deserves with amazing discounts in our Super Sale! Get full root access, a… more info
Seravo 🏆 Alexa 974,283▲ - 📅 - Status: Identified: We have noticed a third party nameserver problem which causes some sites using these nameserver… more info
thenew.org 🏆 Alexa 852,586▲ - 📅 - At PIR, our Core Values are at the root of everything we do. It’s the people behind .ORG that are doing the work to… more info
📋 Latest news about Root Nameserver
ISC Installs Root Nameserver in Mexico - 📅 - Internet Systems Consortium (ISC.org), in conjunction with NIC Mexico, Prodigy Data Center, Avantel and Alestra announced on Monday that it has installed the first root nameserver in Mexico. For the project, NIC Mexico coordinated the efforts to install the server and bandwidth providers Prodigy Data Center, Avantel ...