ObsoletedLegacy stream

RFC 883: Domain names: Implementation specification

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 1034, RFC 1035.

Current document in this lineage: RFC 1034Domain names - concepts and facilities; RFC 1035Domain names - implementation and specification

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

This RFC discusses the implementation of domain name servers and resolvers, specifies the format of transactions, and discusses the use of domain names in the context of existing mail systems and other network software.

Document record

Document ID
RFC883
Published
November 1983
Authors
P. Mockapetris
Status
UNKNOWN
Stream
Legacy
Area
Pages
74
Also known as
Obsoleted by:
RFC 1034, RFC 1035
Updated by:
RFC 973

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

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

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/883-domain-names-implementation-specification