How the Domain Name System Works: Difference between revisions
Dustin Loup (talk | contribs) m Reverted edits by Kiran Kumar (talk) to last revision by Dustin Phillips |
Applied modification ruleset: Corrections using AWB-ICW patterns |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
==Overview== | ==Overview== | ||
The DNS is made up of many servers and databases which, through a series of lookups in various caches, configure [[Domain Name]]s into [[IP Address]]es. The Domain Name System is a distributed database arranged hierarchically; its purpose is to provide a layer of abstraction between Internet services (web, email, etc.) and the numeric addresses (IP addresses) used to uniquely identify any given machine on the Internet. The DNS associates a variety of information with the domain names assigned and, most importantly, translates the domain names meaningful to humans into the numerical identifiers that locate the desired destination. | The DNS is made up of many servers and databases which, through a series of lookups in various caches, configure [[Domain Name]]s into [[IP Address]]es. The Domain Name System is a distributed database arranged hierarchically; its purpose is to provide a layer of abstraction between Internet services (web, email, etc.) and the numeric addresses (IP addresses) used to uniquely identify any given machine on the Internet. The DNS associates a variety of information with the domain names assigned and, most importantly, translates the domain names meaningful to humans into the numerical identifiers that locate the desired destination. | ||
[[PowerDNS]] has a primer on the DNS as it functioned in 2018: [https://powerdns.org/hello-dns/ A warm welcome to DNS] | |||
==History== | |||
The need for a hierarchical [[DNS]] arose with the popularity of the Internet in academic spheres in the early 1980s, which eventually necessitated a decentralized Internet. Communications between [[The Stanford Research Institute NIC]] and other institutions included plans to create a hierarchical [[DNS]], and can be found in [http://www.rfc-editor.org/rfc/rfc805.txt RFC 805], a group document from 1982. This document outlines many of the basics of the eventual [[DNS]], including the need for [[TLD]]s to provide a fixed starting point for queries, and the need for [[SLD]]s to be unique. This, in turn, would necessitate the need for a [[registrar]] type of administration, and help the nascent IT community recognize that the distribution of responsibility for each domain to individual name servers would provide administrative advantages.<ref>[http://www.livinginternet.com/i/iw_dns_history.htm Living Internet]</ref> | |||
==How Does It Work?== | ==How Does It Work?== | ||
| Line 10: | Line 15: | ||
DNS includes three types of top-level domains: generic (gTLD), country code (ccTLD), and sponsored (sTLD). gTLDs include domains that | DNS includes three types of top-level domains: generic (gTLD), country code (ccTLD), and sponsored (sTLD). gTLDs include domains that | ||
could be obtained by anyone (.com, .info, .net, and .org). Since 2014 many other gTLDs have been added like .pub, .ngo, .sucks. sTLDs are limited to a specific group e.g .aero (for air-transport industry). | could be obtained by anyone (.com, .info, .net, and .org). Since 2014 many other gTLDs have been added like .pub, .ngo, .sucks. sTLDs are limited to a specific group e.g. .aero (for air-transport industry). | ||
For each domain, the DNS spreads the responsibility by mapping the domain names and assigning them into IP addresses, and vice-versa. This is accomplished through authoritative name servers which have been designated for each domain. Each authoritative name server is responsible for its own particular domain, but it has the authority to assign new authoritative name servers to any of its sub-domains. The DNS is able to store many types of information, even the mail server lists for a specific domain. The DNS is a core element which ensures the functionality of the Internet through its distributed keyword-based redirection service. | For each domain, the DNS spreads the responsibility by mapping the domain names and assigning them into IP addresses, and vice-versa. This is accomplished through authoritative name servers which have been designated for each domain. Each authoritative name server is responsible for its own particular domain, but it has the authority to assign new authoritative name servers to any of its sub-domains. The DNS is able to store many types of information, even the mail server lists for a specific domain. The DNS is a core element which ensures the functionality of the Internet through its distributed keyword-based redirection service. | ||
| Line 33: | Line 38: | ||
# Location DNS services: to ease visitors' work, increase visitors' satisfaction and strengthen the relationship with all visitors.<ref>[http://www.dns.com/services/ DNS Services]</ref> | # Location DNS services: to ease visitors' work, increase visitors' satisfaction and strengthen the relationship with all visitors.<ref>[http://www.dns.com/services/ DNS Services]</ref> | ||
== | ==Developments and the "DNS Camel"== | ||
In 2012, an [[IETF]] draft proposal, called "DNS Extension for Autonomous Internet (AIP)," was written by three Chinese technologists suggesting a method of operating alternate DNS root servers within national boundaries using gateways for translation. All DNS requests would carry an additional TLD, in order to designate that the requests were being sent to an alternate root. | In 2012, an [[IETF]] draft proposal, called "DNS Extension for Autonomous Internet (AIP)," was written by three Chinese technologists suggesting a method of operating alternate DNS root servers within national boundaries using gateways for translation. All DNS requests would carry an additional TLD, in order to designate that the requests were being sent to an alternate root. The standard would add a single letter to the DNS string - for example, "yahoo.com.B" - to designate the address of the alternate, nationally controlled root.<ref name="ietfaip">[https://datatracker.ietf.org/doc/draft-diao-aip-dns/ IETF Data Tracker - Internet Draft: DNS Extension for Autonomous Internet], expired April 19, 2018</ref> | ||
At the time, critics noted that the proposal would allow greater governmental control over the Internet.<ref>[http://domainincite.com/9474-china-proposes-to-split-up-the-dns China proposes to split up the DNS, domainincite.com]</ref> The Internet Draft expired in April 2018 after eleven proposed revisions.<ref name="ietfaip" /> The draft was one of many efforts to create [[Alternative Roots|alternative root systems]] for the Internet. | |||
The | The [[DNS Camel]] refers to the overloading of features and protocols onto the DNS architecture, such that one small addition will "break the camel's back." | ||
==References== | ==References== | ||
| Line 47: | Line 52: | ||
[[Category: Glossary]] | [[Category: Glossary]] | ||