RFC - 883

DOMAIN NAMES - IMPLEMENTATION and SPECIFICATION

Original:	ftp://ftp.isi.edu/in-notes/rfc883.txt
Authors:	P. Mockapetris [ISI]
Date:	November 1983
Category:	Informational
This specification has been !!! obsoleted !!!

---

Obsoleted by:
RFC-1035std13 [STD 13]	Domain names - implementation and specification (Updated by RFC-1876exp, RFC-1348, RFC-4033prop, RFC-4035prop, RFC-4034prop, RFC-2308prop, RFC-2065, RFC-2845prop, RFC-2181prop, RFC-1995prop, RFC-1996prop, RFC-2535, RFC-4343prop, RFC-3658, RFC-1982prop, RFC-2136prop, RFC-3425prop, RFC-1101, RFC-1183exp, RFC-2137)
RFC-1034std13 [STD 13]	Domain names - concepts and facilities (Updated by RFC-1876exp, RFC-1348, RFC-4033prop, RFC-4035prop, RFC-4034prop, RFC-2308prop, RFC-2065, RFC-2181prop, RFC-2535, RFC-4343prop, RFC-1982prop, RFC-4592prop, RFC-1101, RFC-1183exp)

Updated by:
RFC-973	Domain system changes and observations (Obsoleted by RFC-1034std13, RFC-1035std13)

Referred by:	35 RFC
Refers to:	12 RFC

---

Abstract

        +-----------------------------------------------------+
        |                                                     |
        | This memo 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.                                   |
        |                                                     |
        | This memo assumes that the reader is familiar with  |
        | RFC 882(-> 1035std13 | 1034std13), "Domain Names - Concepts and Facilities"   |
        | which discusses the basic principles of domain      |
        | names and their use.                                |
        |                                                     |
        | The algorithms and internal data structures used in |
        | this memo are offered as suggestions rather than    |
        | requirements; implementers are free to design their |
        | own structures so long as the same external         |
        | behavior is achieved.                               |
        |                                                     |
        +-----------------------------------------------------+

           +-----------------------------------------------+
           |                                               |
           |             *****  WARNING  *****             |
           |                                               |
           | This RFC contains format specifications which |
           | are preliminary and are included for purposes |
           | of explanation only.  Do not attempt to use   |
           | this information for actual implementations.  |
           |                                               |
           +-----------------------------------------------+

---