RFC 883

RFC 883
Title	Domain Names - Implementation and Specification
Number	883
Author	Paul Mockapetris
Publisher	IETF
Series	RFC
Pub date	November 1983
Status	Obsolete
Obsoletes	RFC 882
Obsoleted by	RFC 1034, RFC 1035

RFC 883. Published in November 1983 and authored by Paul Mockapetris, this document, along with its companion RFC 882, formally defined the Domain Name System (DNS) for the ARPANET. It provided the first complete technical specification for implementing the DNS, detailing the protocols and formats for name resolution and server operations. This foundational work established the operational framework that would evolve into the global directory service underpinning the modern Internet.

Overview

RFC 883 served as the concrete implementation guide for the architectural concepts outlined in RFC 882. Its primary goal was to specify the on-the-wire protocols, message formats, and expected behaviors for DNS servers and DNS clients. The document was produced under the auspices of the IETF and represented a critical step in transitioning from the aging HOSTS.TXT file system managed by the SRI-NIC. It described a distributed, hierarchical database designed to map human-readable domain names to numerical IP addresses and other resource records, enabling scalable growth of the ARPANET and its successor networks.

Technical Specifications

The core of the document detailed the DNS message structure, including the layout of the header, question, answer, authority, and additional sections. It specified opcodes and response codes for communicating success or failure states like SERVFAIL and NXDOMAIN. The protocol mandated the use of UDP as the primary transport on port 53, with provisions for fallback to TCP for larger responses such as zone transfers. It defined essential resource record types including the A record for host addresses, CNAME record for aliases, and the NS record for delegating authority to other name servers. The specification also covered message compression techniques to reduce packet size.

Key Concepts and Terminology

RFC 883 established the fundamental lexicon of the DNS. It formally defined a domain name as a sequence of labels and introduced the concept of a fully qualified domain name (FQDN). The document explained the roles of different server types, including authoritative name servers, which hold definitive data for a zone, and recursive resolvers, which traverse the hierarchy on behalf of clients. Key operational concepts included TTL (Time to Live) values for caching, the use of UDP for queries, and the process of recursion and iteration. It also described the in-addr.arpa domain for reverse lookups.

Relationship to Other Protocols

The DNS specified was designed as an application-layer protocol tightly integrated with the existing Internet protocol suite. Its reliance on UDP and TCP placed it alongside other core protocols like SMTP and FTP. It directly replaced the function of the HOSTS.TXT system and was a prerequisite for the scalability of electronic mail systems using RFC 821. The protocol's success influenced later IETF standards, including those for DHCP and IPv6, which required compatible DNS extensions. Its design principles were later reflected in directory services like LDAP.

Implementation and Deployment

The first reference implementation, known as BIND (Berkeley Internet Name Domain), was developed at the University of California, Berkeley by a team including Douglas Terry, Mark Painter, and David Riggle. Early deployment occurred on the ARPANET and CSNET, with root servers initially administered by the ISI. Deployment challenges included coordinating the transition from the old HOSTS.TXT system, establishing consistent zone file administration, and ensuring interoperability between different early server software. The operational experience gained from these deployments directly informed the revisions that led to RFC 1034 and RFC 1035.

Impact and Historical Significance

RFC 883, together with RFC 882, is considered one of the most influential documents in Internet history. It solved the critical scalability problem of the ARPANET, enabling the transition to the global Internet. By decentralizing administration, it fostered the explosive growth of registrations under top-level domains like .com, .edu, and .org. The system it defined became an indispensable utility, comparable in importance to TCP/IP itself. While obsoleted by RFC 1034 and RFC 1035 in 1987, its core architecture remains intact, a testament to its robust design by Paul Mockapetris and the early IETF community.

Category:Internet Standards Category:Request for Comments Category:Domain Name System