metasystema.org
UpdatedINTERNET STANDARDLegacy streamSTD13

RFC 1034: Domain names - concepts and facilities

Still current, but amended. Parts of this document are changed or extended by RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 2065, RFC 2181, RFC 2308, RFC 2535, RFC 4033, RFC 4034, RFC 4035, RFC 4343, RFC 4592, RFC 5936, RFC 8020, RFC 8482, RFC 8767, RFC 9471. Read both.

In plain English — editorial summary, not part of the RFC

RFC 1034 lays out the concepts and structure of the Domain Name System: the tree of domain names, zones and delegation, resource records, and how resolvers walk from the root down to an answer. It is the conceptual half of DNS; RFC 1035 gives the wire format.

Original abstract from the RFC

This RFC is the revised basic definition of The Domain Name System. It obsoletes RFC-882. This memo describes the domain style names and their used for host address look up and electronic mail forwarding. It discusses the clients and servers in the domain name system and the protocol used between them.

Document record

Document ID
RFC1034
Published
November 1987
Authors
P. Mockapetris
Status
INTERNET STANDARD
Stream
Legacy
Area
—
Pages
55
Also known as
STD13
Obsoletes:
RFC 882, RFC 883, RFC 973
Updated by:
RFC 1101, RFC 1183, RFC 1348, RFC 1876, RFC 1982, RFC 2065, RFC 2181, RFC 2308, RFC 2535, RFC 4033, RFC 4034, RFC 4035, RFC 4343, RFC 4592, RFC 5936, RFC 8020, RFC 8482, RFC 8767, RFC 9471

Topics

Standards lineage

This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.

  1. RFC 882 (1983)
  2. RFC 883 (1983)
  3. RFC 973 (1986)
  4. RFC 1034 (1987)
  5. RFC 1035 (1987) ✓

Read the full history of Domain names - implementation and specification →

Referenced by

19 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/1034-domain-names-concepts-and-facilities