Jump to content

DNS root zone

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by 2605:b100:d18:79ad:753d:8687:5163:fb01 (talk) at 23:46, 19 September 2021. The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The DNS root zone is the top-level DNS zone in the hierarchical namespace of the Domain Name System (DNS) of the Internet.

Before 1 October 2016, the root zone had been overseen by the Internet Corporation for Assigned Names and Numbers (ICANN) which delegates the management to a subsidiary acting as the Internet Assigned Numbers Authority (IANA).[1] Distribution services are provided by Verisign. Prior to this, ICANN performed management responsibility under oversight of the National Telecommunications and Information Administration (NTIA), an agency of the United States Department of Commerce.[2] Oversight responsibility transitioned to the global stakeholder community represented within ICANN's governance structures.

A combination of limits in the DNS definition and in certain protocols, namely the practical size of unfragmented User Datagram Protocol (UDP) packets, resulted in a practical maximum of 13 root name server addresses that can be accommodated in DNS name query responses. However the root zone is serviced by several hundred servers at over 130 locations in many countries.[3][4]

Initialization of DNS service

The DNS root zone is served by thirteen root server clusters which are authoritative for queries to the top-level domains of the Internet.[5][6] Thus, every name resolution either starts with a query to a root server or uses information that was once obtained from a root server.

The root servers clusters have the official names a.root-servers.net to m.root-servers.net.[6] To resolve these names into addresses, a DNS resolver must first find an authoritative server for the net zone. To avoid this circular dependency, the address of at least one root server must be known for bootstrapping access to the DNS. For this purpose operating systems or DNS server or resolver software packages typically include a file with all addresses of the DNS root servers. Even if the IP addresses of some root servers change, at least one is needed to retrieve the current list of all name servers. This address file is called named.cache in the BIND name server reference implementation. The current official version is distributed by ICANN's InterNIC.[7]

With the address of a single functioning root server, all other DNS information may be discovered recursively, and information about any domain name may be found.

Redundancy and diversity

The root DNS servers are essential to the function of the Internet, as most Internet services, such as the World Wide Web and electronic-mail, are based on domain names. The DNS servers are potential points of failure for the entire Internet. For this reason, multiple root servers are distributed worldwide.[8] The DNS packet size of 512 octets limits a DNS response to thirteen addresses, until protocol extensions (see Extension Mechanisms for DNS) lifted this restriction.[9] While it is possible to fit more entries into a packet of this size when using label compression, thirteen was chosen as a reliable limit. Since the introduction of IPv6, the successor Internet Protocol to IPv4, previous practices are being modified and extra space is filled with IPv6 name servers.

The root name servers are hosted in multiple secure sites with high-bandwidth access to accommodate the traffic load. At first, all of these installations were located in the United States; however, the distribution has shifted and this is no longer the case.[10] Usually each DNS server installation at a given site is a cluster of computers with load-balancing routers.[9] A comprehensive list of servers, their locations and properties is available at https://root-servers.org/. As of February 20th, 2019, there were 938 root servers worldwide.[11]

The modern trend is to use anycast addressing and routing to provide resilience and load balancing across a wide geographic area. For example, the j.root-servers.net server, maintained by Verisign, is represented by 104 (as of January 2016) individual server systems located around the world, which can be queried using anycast addressing.[12]

Management

The content of the Internet root zone file is coordinated by a subsidiary of ICANN which performs the Internet Assigned Numbers Authority (IANA) functions. Verisign generates and distributes the zone file to the various root server operators.

In 1997, when the Internet was transferred from U.S. government control to private hands, NTIA has exercised stewardship over the root zone. A 1998 Commerce Department document stated the agency was "committed to a transition that will allow the private sector to take leadership for DNS management" by the year 2000, however, no steps to make the transition happen were taken. In March 2014, NTIA announced it will transition its stewardship to a "global stakeholder community".[5]

According to Assistant Secretary of Commerce for Communications and Information, Lawrence E. Strickling, March 2014 was the right time to start a transition of the role to the global Internet community. The move came after pressure in the fallout of revelations that the United States and its allies had engaged in surveillance. The chairman of the board of ICANN denied the two were connected, however, and said the transition process had been ongoing for a long time. ICANN president Fadi Chehadé called the move historic and said that ICANN will move toward multi-stakesholder control. Various prominent figures in Internet history, not affiliated with ICANN, also applauded the move.[5]

NTIA's announcement did not immediately affect how ICANN performs its role.[5][13] On March 11, 2016 NTIA announced that it had received a proposed plan to transition its stewardship role over the root zone, and would review it in the next 90 days.[14]

The proposal was adopted, and ICANN's renewed contract to perform the IANA function lapsed on September 30, 2016, resulting in the transition of oversight responsibility to the global stakeholder community represented within ICANN's governance structures. As a component of the transition plan,[15] it created a new subsidiary called Public Technical Identifiers (PTI) to perform the IANA functions which include managing the DNS root zone.

Signing of the root zone

Since July 2010, the root zone has been signed with a DNSSEC signature,[16] providing a single trust anchor for the Domain Name System that can in turn be used to provide a trust anchor for other public key infrastructure (PKI). The root zone DNSKEY section is re-signed periodically with the root zone key signing key performed in a verifiable manner in front of witnesses in a key signing ceremony.[17][18] The KSK2017 with ID 20326 is valid as of 2020.

See also

References

  1. ^ "Stewardship of IANA Functions Transitions to Global Internet Community as Contract with U.S. Government Ends". 2016-10-01. Retrieved 2017-12-25.
  2. ^ Jerry Brito (2011-03-05). "ICANN vs. the World". TIME. Archived from the original on December 30, 2010. Retrieved 2011-12-17.
  3. ^ "There are not 13 root servers". www.icann.org. Retrieved 2018-01-18.
  4. ^ "DNS root servers in the world « stupid.domain.name". stupid.domain.name. Retrieved 2018-01-18.
  5. ^ a b c d Farivar, Cyrus (14 March 2014). "In sudden announcement, US to give up control of DNS root zone". Ars Technica. Retrieved 15 March 2014.
  6. ^ a b "Root Servers". IANA. Retrieved January 17, 2020.
  7. ^ "named.cache". InterNIC. 2015-11-17. Retrieved 2015-11-17.
  8. ^ "SANS Institute InfoSec Reading Room". SANS. Retrieved March 17, 2014.
  9. ^ a b Bradley Mitchell (November 19, 2008). "Why There Are Only 13 DNS Root Name Servers". About.com. Retrieved March 17, 2014.
  10. ^ "DNS Root Servers: The most critical infrastructure on the internet". Slash Root. November 15, 2013.
  11. ^ "Root Servers Technical Operations Assn". Archived from the original on 2017-08-24. Retrieved 2016-01-13.
  12. ^ "Root Server Technical Operations Assn".
  13. ^ "An Update on the IANA Transition". National Telecommunications and Information Administration. 2015-08-17. Retrieved 2015-11-17.
  14. ^ Strickling, Lawrence. "Reviewing the IANA Transition Proposal". National Telecommunications and Information Administration. United States Department of Congress. Retrieved 26 May 2016.
  15. ^ "Proposal to Transition the Stewardship of the Internet Assigned Numbers Authority (IANA) Functions from the U.S. Commerce Department's National Telecommunications and Information Administration (NTIA) to the Global Multistakeholder Community" (PDF). March 2016.
  16. ^ "Root DNSSEC: Information about DNSSEC for the Root Zone". Internet Corporation For Assigned Names and Numbers. Retrieved 2014-03-19.
  17. ^ "First KSK Ceremony". Internet Corporation For Assigned Names and Numbers. 2010-04-18. Archived from the original on 2015-04-14. Retrieved 2014-10-19.
  18. ^ "Root KSK Ceremonies". Internet Assigned Numbers Authority. 2015-11-12. Retrieved 2015-11-17.
  • RFC 2870 – Root Name Server Operational Requirements
  • RFC 2826 – IAB Technical Comment on the Unique DNS Root

Further reading

Wikimedia Commons has media related to DNS root zone.
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=DNS_root_zone&oldid=1045316429"