DNS (protocol)

DNS (protocol)
Name	DNS
Caption	DNS query and response flow
Developer	Paul Mockapetris, Jon Postel
Introduced	1983
Standard	RFC 1034; RFC 1035

DNS (protocol) Domain Name System (DNS) is a hierarchical, distributed naming system translating human-readable names into network identifiers. It underpins the operation of the Internet by mapping domain names to IP addresses, mail routing, service discovery and other resource data, and is specified in foundational engineering documents such as RFC 1034 and RFC 1035.

Overview

The system provides a namespace organized into zones rooted at the Root Zone (DNS), delegating authority to top-level domain operators like Internet Corporation for Assigned Names and Numbers, country code managers such as Nominet and DENIC, and registrars like Verisign and GoDaddy. Client software including BIND resolvers, operating systems like Microsoft Windows and Linux distributions, and applications such as Mozilla Firefox and Google Chrome issue queries over transport layers like User Datagram Protocol and Transmission Control Protocol to authoritative servers operated by cloud providers like Amazon Web Services, Cloudflare, and Google Public DNS.

History and development

The protocol was designed in the early 1980s by engineers at institutions such as University of California, Irvine and the Information Sciences Institute; principal contributors include Paul Mockapetris and Jon Postel, who worked within contexts like the ARPANET and standards bodies including the Internet Engineering Task Force and the Internet Assigned Numbers Authority. Key milestones involved publication of RFCs and operational shifts: the introduction of hierarchical delegation, the creation of top-level domains at Stanford University and transition of management to IANA, and later commercialization and expansion through events like the rollout of new generic TLDs overseen by ICANN.

Protocol architecture and operation

The architecture separates roles among resolvers, recursive resolvers, and authoritative name servers such as primary (master) and secondary (slave) implementations often running software like BIND, Unbound, PowerDNS, or server platforms from Microsoft. The namespace hierarchy includes the root, generic top-level domains (gTLDs) like .com and country-code TLDs (ccTLDs) like .uk administered by organizations such as Nominet UK. Protocol messages exchanged over port 53 contain header fields and sections for question, answer, authority, and additional, as originally defined in specifications published through the IETF working groups.

Resource records and data types

Data are encoded in resource records (RRs) with common types such as A record, AAAA record, CNAME record, MX record, NS record, PTR record, SOA record and newer types like TXT record and SRV record. Specialized records and extensions include DNSSEC-related records (RRSIG, DNSKEY, DS) developed and standardized within the IETF and records supporting service discovery used by projects from Microsoft and Apple for local name resolution and service advertisement.

Resolution process and caching

Resolution proceeds via iterative or recursive queries where stub resolvers in client hosts consult recursive resolvers operated by ISPs, enterprises, or public services such as Google Public DNS and Cloudflare; when necessary a resolver traverses the hierarchy from the root zone through TLD servers to authoritative servers like those run by registrars or hosting providers such as Amazon Route 53. Time-to-live values in RRs determine caching behavior implemented in software like BIND and Unbound and in operating systems such as Windows Server DNS and systemd-resolved, affecting query volume and administrative practices used by network operators including Cisco and Juniper Networks.

Security and extensions

Security enhancements include DNSSEC for data origin authentication and integrity, extensions to transport security such as DNS over HTTPS and DNS over TLS promoted by organizations like Mozilla Foundation, Google, and Cloudflare, and mechanisms to mitigate threats like cache poisoning exposed in incidents such as analyses by CERT Coordination Center and the SANS Institute. Additional measures involve response rate limiting, access control lists in server software from ISC and commercial vendors, and operational best practices recommended by bodies like the IETF and ICANN.

Implementation and deployment practices

Deployments vary from enterprise clusters using authoritative appliances from vendors such as F5 Networks and Infoblox to cloud-native services provided by Amazon Web Services and Google Cloud Platform. Operators manage zone data via tools including git workflows, automation systems like Ansible and Terraform, and registrar interfaces governed by policies set by registry operators such as Verisign and overseen by ICANN. Monitoring, logging and analytics often integrate with platforms like Prometheus and ELK Stack to track query patterns, performance, and abuse mitigations used by network teams at organizations including Facebook, Netflix, and Akamai.

Category:Internet protocols