RFC 882

RFC 882. Authored by Paul Mockapetris and published by the Internet Engineering Task Force in November 1983, this foundational document introduced the conceptual framework for the Domain Name System. It outlined the core architectural principles for translating human-readable hostnames into machine-readable IP addresses, addressing critical scalability limitations of the earlier HOSTS.TXT system maintained by the Network Information Center. The specifications within it laid the groundwork for a distributed, hierarchical database that would become a cornerstone of the modern Internet.

Overview

The primary objective was to design a scalable replacement for the centralized and manually updated HOSTS.TXT file, which was becoming unmanageable with the growth of the ARPANET. It proposed a distributed naming system where authority for subsets of the namespace, known as domains, could be delegated to different organizations. This system introduced the concepts of resource records, name servers, and resolvers, establishing a client-server model for name resolution. The design emphasized robustness, avoiding a single point of failure, and aimed to support various types of network data beyond simple hostname-to-address mapping.

Technical Specifications

The document formally defined the structure of domain names as labels separated by dots, organized in a hierarchical tree structure descending from a conceptual root. It specified the roles of different components, including authoritative name servers that store data for specific zones and resolvers that act as clients querying this distributed database. Key data structures called resource records were introduced to hold information such as addresses and mail exchanges. The protocol for communication between resolvers and servers was described, involving queries and responses carried within standard IP datagrams, often using the User Datagram Protocol.

Historical Context and Development

The development was driven by the impending collapse of the HOSTS.TXT system administered by the Stanford Research Institute's Network Information Center. Following earlier discussions in documents like RFC 799 and RFC 819, Paul Mockapetris of the University of Southern California's Information Sciences Institute was tasked with creating a new design. His work built upon ideas from existing systems like ZOG and GCCS, but proposed a uniquely flexible and distributed architecture. The release was swiftly followed by a companion document, RFC 883, which provided further implementation details, forming the initial complete specification for the Domain Name System.

Impact and Legacy

Its publication marked the definitive beginning of the Domain Name System, one of the most critical and enduring protocols in the history of computer networking. The hierarchical and delegated architecture enabled the explosive, global growth of the Internet by allowing scalable and decentralized management of names. Core concepts like top-level domains (e.g., .com, .org, .edu), second-level domains, and the client-server resolution model became permanent fixtures of the network. It directly influenced the creation of the first operational root name servers and established the operational practices for entities like the Internet Assigned Numbers Authority.

Deprecation and Successors

It was declared obsolete within a very short timeframe, superseded by its immediate companion, RFC 883, in November 1983. Both of these initial documents were later replaced and vastly expanded by the definitive DNS standards, RFC 1034 and RFC 1035, authored again by Paul Mockapetris in 1987. These successor documents refined the original concepts, introduced new resource record types, and fully standardized the protocol. The core architecture and terminology established, however, remain fundamentally intact and in continuous worldwide operation, managed by organizations like the Internet Corporation for Assigned Names and Numbers.

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