RFC 1035

RFC 1035
Title	RFC 1035
Author	Paul Mockapetris, Mark Davis
Published	November 1987
Series	RFC
Subject	Domain Name System

RFC 1035 RFC 1035 is a key Internet standards document that defines elements of the Domain Name System naming and resource record formats used in the Internet Engineering Task Force protocols and implementations. It complements contemporaneous standards developed in the Internet Engineering Task Force and ARPANET research, informing implementations by vendors such as Sun Microsystems, IBM, Microsoft Corporation, and researchers at institutions including MIT, Stanford University, and the University of California, Berkeley. RFC 1035 remains influential across protocols maintained by organizations such as the Internet Assigned Numbers Authority, Internet Society, IETF Working Group, and standards referenced in later documents from the World Wide Web Consortium and Internet Research Task Force.

Background and Context

RFC 1035 was published in the historical era of early Internet engineering alongside RFCs like RFC 1034 and grew out of work on ARPANET naming and the need for scalable hostname resolution across networks connecting sites such as DARPA, NASA, Bell Labs, and university research centers. The authors drew on operational experience from network operators at Bolt, Beranek and Newman, researchers at Xerox PARC, and engineers working on the precursor protocols specified by groups such as the International Organization for Standardization and Electronic Frontier Foundation-adjacent projects. The specification sits in the lineage of networking standards that include the Transmission Control Protocol, User Datagram Protocol, and early routing efforts like Routing Information Protocol and Border Gateway Protocol, reflecting discussions from meetings of the Internet Engineering Task Force and the Network Working Group.

Specification Overview

RFC 1035 defines the wire formats, name syntax, and semantics for DNS messages and resource records used by resolvers and authoritative servers. It prescribes how hosts and servers from vendors such as Cisco Systems, Juniper Networks, and Hewlett-Packard implement lookup behavior consistent with expectations arising from projects at Bell Labs and standards bodies including the IETF and Internet Architecture Board. The document describes message header fields, question and answer sections, and rules for authoritative delegation and caching that influenced implementations in software like BIND, Microsoft DNS Server, and various UNIX resolver libraries derived from Berkeley Software Distribution distributions and FreeBSD.

DNS Message Formats and Protocol

RFC 1035 specifies DNS message layout on the wire, including header flags, counts, and resource record encoding for transport over User Datagram Protocol and potential use with Transmission Control Protocol. The header format and flags were designed with considerations similar to earlier protocol specifications such as RFC 791 and influenced later designs associated with IETF Working Group discussions and operational practice at operators like AT&T and Verizon Communications. Compression schemes and name representations were crafted to minimize packet size for networking hardware from vendors like DEC and to interoperate with resolver stacks developed at institutions such as Carnegie Mellon University and Princeton University.

Resource Record Types and Semantics

RFC 1035 enumerates core resource record types including the address mapping record used by hosts in environments exemplified by X.509-adjacent name resolution needs and administrative records used by name servers in deployments at entities such as Amazon Web Services and Google LLC. It defines semantics for records used in delegation, zone management, and mail routing with ties to operational practices at USENIX-affiliated operators and recommendations that informed DNSSEC-related work at IETF and cryptographic communities like RSA Laboratories. The record types and conventions in the RFC influenced zone file formats used by server software from ISC and management tools developed by vendors such as Red Hat and Canonical.

Implementation and Interoperability

Implementers from organizations including Internet Systems Consortium, Microsoft Corporation, Apple Inc., and open source projects across GNU Project ecosystems used RFC 1035 as a reference for interoperability testing, conformance efforts, and interoperability events run in partnership with the IETF and regional registries like RIPE NCC and APNIC. The RFC’s clear byte-level definitions enabled cross-platform compatibility across machines running operating systems such as UNIX, Linux, BSD, and early Windows NT variants. Interoperability challenges described in operational experience reports at conferences like Usenix Annual Technical Conference led to errata and later recommendations captured in successor RFCs and standards work maintained by the Internet Engineering Task Force.

Security and Limitations

While RFC 1035 established foundational norms for DNS operation, it did not address later security mechanisms such as authenticated denial of existence, transaction security, or cryptographic validation later formalized by efforts like DNSSEC and work published by the IETF DNS Extensions Working Group. Operational vulnerabilities observed in deployments at major service providers including Cloudflare and Akamai Technologies prompted subsequent protocol extensions and mitigations standardized by the IETF and implemented by vendors such as Cisco Systems and Fortinet. Constraints on message size, ambiguity in caching semantics, and lack of built-in integrity checks highlighted limitations acknowledged in later documents and security analyses presented at venues including Black Hat and RSA Conference.

Category:Internet standards