Name server

Aname serveris a computer application that implements anetwork servicefor providing responses to queries against adirectory service.It translates an often humanly meaningful, text-based identifier to a system-internal, often numeric identification or addressing component. This service is performed by the server in response to aservice protocolrequest.

An example of a name server is the server component of theDomain Name System(DNS), one of the two principalnamespacesof theInternet.The most important function of DNS servers is the translation (resolution) of human-memorabledomain namesandhostnamesinto the corresponding numericInternet Protocol(IP) addresses, the second principal name space of the Internet which is used to identify and locate computer systems and resources on the Internet.

Domain name server

The Internet maintains two principalnamespaces:the domain name hierarchy^[1]and the IP address system.^[2]The Domain Name System maintains the domain namespace and provides translation services between these two namespaces. Internet name servers implement the Domain Name System.^[3]The top hierarchy of the Domain Name System is served by theroot name serversmaintained by delegation by theInternet Corporation for Assigned Names and Numbers(ICANN). DNS servers, which are located all over the world, translate domain names into IP addresses, giving them control over which server a user may access via a given domain. Below the root, Internet resources are organized into a hierarchy of domains, administered by the respective registrars and domain name holders. A DNS name server is a server that stores theDNS records,such as address (A, AAAA) records, name server (NS) records, and mail exchanger (MX) records for a domain name (see alsoList of DNS record types) and responds with answers to queries against its database.

Types of name servers

Name servers are usually eitherauthoritativeorrecursive,as described below.

Although not the usual practice today, name servers can be both authoritativeandrecursive, if they are configured to give authoritative answers to queries in some zones, while acting as acaching name serverfor all other zones.^[4]

Authoritative name server

An authoritative name server is a name server that is responsible for givinganswersin response to questions asked about names in azone.An authoritative-only name server returns answers only to queries about domain names in that it is responsible for (as specifically configured by its administrator).

An authoritative name server can either be aprimaryserver or asecondaryserver. A primary server for a zone is the server that stores the definitive versions of all records in that zone. It is identified in the start-of-authority (SOA) resource record. A secondary server for a zone uses an automatic updating mechanism to maintain an identical copy of the primary server's database for a zone. Examples of such mechanisms includeDNS zone transfersand file transfer protocols. DNS provides a mechanism whereby the primary for a zone can notify all the known secondaries for that zone when the contents of the zone have changed. The contents of a zone are either manually configured by an administrator, or managed usingDynamic DNS.^[5]

Every domain name appears in a zone served by one or more authoritative name servers. Thefully qualified domain namesof the authoritative name servers of a zone are listed in the NS records of that zone. If the server for a zone is not also authoritative for its parent zone, the server for the parent zone must be configured with adelegationfor the zone.^[6]

When a domain is registered with adomain name registrar,the zone administrator provides the list of name servers (typically at least two, for redundancy^[7]) that are authoritative for the zone that contains the domain. The registrar provides the names of these servers to thedomain registryfor thetop-level domaincontaining the zone. The domain registry in turn configures the authoritative name servers for that top-level domain with delegations for each server for the zone. If the fully qualified domain name of any name server for a zone appears within that zone, the zone administrator provides IP addresses for that name server, which are installed in the parent zone asglue records;otherwise, the delegation consists of the list of NS records for that zone.^[8]

Authoritative answer

A name server indicates that its response is authoritative by setting theAuthoritative Answer(AA) bit in the response to a query on a name for which it is authoritative. Name servers providing answers for which they are not authoritative (for example, name servers for parent zones) do not set theAAbit.^[3]

Recursive Resolver

ARecursive Resolver(sometimes called a Recursive Name Server) is a DNS name server that accepts recursive queries (defined below) from clients (who are using a stub resolver), and then resolves those queries, either from a cache of prior results, or by asking one or more authoritative servers.

Recursive query

If a name server cannot answer a query because it does not contain an entry for the host in its DNS cache, it may recursively query name servers higher up in the hierarchy.^[9]This is known as arecursive queryorrecursive lookup.A server providing recursive queries is known as arecursive name serverorrecursive DNS,sometimes abbreviated asrecdns.^[10]

In principle, authoritative name servers suffice for the operation of the Internet. However, with only authoritative name-servers operating, every DNS query must start with recursive queries at theroot zoneof the Domain Name System and each user system must implement resolver software capable of recursive operation.^{[clarification needed]}

Caching name server

Caching name servers (DNS caches) are usually recursive resolvers that store DNS query results for a period of time determined in the configuration (time-to-live) of each domain-name record. DNS caches improve the efficiency of the DNS by reducing DNS traffic across the Internet, and by reducing load on authoritative name-servers, particularly root name-servers. Because they can answer questions more quickly, they also increase the performance of end-user applications that use the DNS.

Caching name servers are often also recursive name servers—they perform every step necessary to answer any DNS query they receive. To do this the name server queries each authoritative name-server in turn, starting from the DNS root zone. It continues until it reaches the authoritative server for the zone that contains the queried domain name. That server provides the answer to the question, or definitively says it can't be answered, and thecaching resolverthen returns this response to the client that asked the question. The authority, resolving and caching functions can all be present in a DNS server implementation, but this is not required: a DNS server can implement any one of these functions alone, without implementing the others. Internet service providerstypically provide caching resolvers for their customers. In addition, manyhome-networkingrouters implement caching resolvers to improve efficiency in the local network. Some systems utilizenscd,which stands for the "name service caching daemon".^[11]

References

^RFC 1034,Domain Names—Concepts and Facilities,P. Mockapetris, The Internet Society (November 1987)
^RFC 781,Internet Protocol—DARPA Internet Program Protocol Specification,Information Sciences Institute, J. Postel (Ed.), The Internet Society (September 1981)
^^a ^bRFC 1035,Domain Names — Implementation and Specification,P. Mockapetris, The Internet Society (November 1987)
^Paul Hoffman; Andrew Sullivan; Kazunori Fujiwara (January 2019).DNS Terminology.IETF.BCP 219.Retrieved17 December2015.
^Yakov Rekhter; Susan Thomson; Jim Bound; Paul Vixie (April 1007).Dynamic Updates in the Domain Name System (DNS Update).IETF.doi:10.17487/RFC2136.RFC 2136.Retrieved17 December2015.
^Robert Elz; Randy Bush (July 1997).Clarifications to the DNS Specification.IETF.doi:10.17487/RFC2181.RFC 2181.Retrieved17 December2015.
^"Name Server definition at techterms".
^Paul Mockapetris (November 1987)."Technical considerations".Domain Names - Domain Concepts and Facilities.IETF.sec. 4.2.1.doi:10.17487/RFC1034.RFC 1034.Retrieved17 December2015.
^"Composite Application Manager for Internet Service Monitoring, Reference Guide".IBM.Retrieved15 February2012.
^"Network setup for Cambridge's new DNS servers".Retrieved2018-02-05.The recursive DNS server (aka recdns)
^,though this is typically not used for caching DNS names. Nemeth, Evi;Snyder, Garth; Heine, Tra. (2006).Linux administration handbook(2 ed.). Addison-Wesley Professional. p. 504e.ISBN 978-0-13-148004-9.Retrieved2012-02-14.ncsd [.....] cache[s] the results of DNS lookups [...] but it also wraps the library routines that access information from thepasswdandgroupfiles and their network database equivalents.{{cite book}}:Check|url=value (help)

External links

Free and Public DNS Servers Archived2016-10-15 at theWayback Machine,article onaboutby Tim Fisher, retrieved on 2015-02-08 21-59 UTC
DNS & BIND Resources Archived2006-09-02 at theWayback Machine

[rfc1034-1] RFC 1034,Domain Names—Concepts and Facilities,P. Mockapetris, The Internet Society (November 1987)

[rfc781-2] RFC 781,Internet Protocol—DARPA Internet Program Protocol Specification,Information Sciences Institute, J. Postel (Ed.), The Internet Society (September 1981)

[rfc1035-3] RFC 1035,Domain Names — Implementation and Specification,P. Mockapetris, The Internet Society (November 1987)

[4] Paul Hoffman; Andrew Sullivan; Kazunori Fujiwara (January 2019).DNS Terminology.IETF.BCP 219.Retrieved17 December2015.

[5] Yakov Rekhter; Susan Thomson; Jim Bound; Paul Vixie (April 1007).Dynamic Updates in the Domain Name System (DNS Update).IETF.doi:10.17487/RFC2136.RFC 2136.Retrieved17 December2015.

[6] Robert Elz; Randy Bush (July 1997).Clarifications to the DNS Specification.IETF.doi:10.17487/RFC2181.RFC 2181.Retrieved17 December2015.

[techterms-7] "Name Server definition at techterms".

[8] Paul Mockapetris (November 1987)."Technical considerations".Domain Names - Domain Concepts and Facilities.IETF.sec. 4.2.1.doi:10.17487/RFC1034.RFC 1034.Retrieved17 December2015.

[:0-9] "Composite Application Manager for Internet Service Monitoring, Reference Guide".IBM.Retrieved15 February2012.

[10] "Network setup for Cambridge's new DNS servers".Retrieved2018-02-05.The recursive DNS server (aka recdns)

[11] ,though this is typically not used for caching DNS names. Nemeth, Evi;Snyder, Garth; Heine, Tra. (2006).Linux administration handbook(2 ed.). Addison-Wesley Professional. p. 504e.ISBN 978-0-13-148004-9.Retrieved2012-02-14.ncsd [.....] cache[s] the results of DNS lookups [...] but it also wraps the library routines that access information from thepasswdandgroupfiles and their network database equivalents.{{cite book}}:Check|url=value (help)

[1]

[2]

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]