Domain administrators guide
RFC 1032

Document Type RFC - Unknown (November 1987; No errata)
Last updated 2013-03-02
Stream Legacy stream
Formats plain text html pdf htmlized (tools) htmlized bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1032 (Unknown)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                       M. Stahl
Request for Comments: 1032                         SRI International
                                                       November 1987



   This memo describes procedures for registering a domain with the
   Network Information Center (NIC) of Defense Data Network (DDN), and
   offers guidelines on the establishment and administration of a domain
   in accordance with the requirements specified in RFC-920.  It is
   intended for use by domain administrators.  This memo should be used
   in conjunction with RFC-920, which is an official policy statement of
   the Internet Activities Board (IAB) and the Defense Advanced Research
   Projects Agency (DARPA).  Distribution of this memo is unlimited.


   Domains are adminstrative entities that provide decentralized
   management of host naming and addressing.  The domain-naming system
   is distributed and hierarchical.

   The NIC is designated by the Defense Communications Agency (DCA) to
   provide registry services for the domain-naming system on the DDN and
   DARPA portions of the Internet.

   As registrar of top-level and second-level domains, as well as
   administrator of the root domain name servers on behalf of DARPA and
   DDN, the NIC is responsible for maintaining the root server zone
   files and their binary equivalents.  In addition, the NIC is
   responsible for administering the top-level domains of "ARPA," "COM,"
   "EDU," "ORG," "GOV," and "MIL" on behalf of DCA and DARPA until it
   becomes feasible for other appropriate organizations to assume those

   It is recommended that the guidelines described in this document be
   used by domain administrators in the establishment and control of
   second-level domains.


   The role of the domain administrator (DA) is that of coordinator,
   manager, and technician.  If his domain is established at the second
   level or lower in the tree, the DA must register by interacting with
   the management of the domain directly above his, making certain that

Stahl                                                           [Page 1]
RFC 1032              DOMAIN ADMINISTRATORS GUIDE          November 1987

   his domain satisfies all the requirements of the administration under
   which his domain would be situated.  To find out who has authority
   over the name space he wishes to join, the DA can ask the NIC
   Hostmaster.  Information on contacts for the top-level and second-
   level domains can also be found on line in the file NETINFO:DOMAIN-
   CONTACTS.TXT, which is available from the NIC via anonymous FTP.

   The DA should be technically competent; he should understand the
   concepts and procedures for operating a domain server, as described
   in RFC-1034, and make sure that the service provided is reliable and
   uninterrupted.  It is his responsibility or that of his delegate to
   ensure that the data will be current at all times.  As a manager, the
   DA must be able to handle complaints about service provided by his
   domain name server.  He must be aware of the behavior of the hosts in
   his domain, and take prompt action on reports of problems, such as
   protocol violations or other serious misbehavior.  The administrator
   of a domain must be a responsible person who has the authority to
   either enforce these actions himself or delegate them to someone

   Name assignments within a domain are controlled by the DA, who should
   verify that names are unique within his domain and that they conform
   to standard naming conventions.  He furnishes access to names and
   name-related information to users both inside and outside his domain.
   He should work closely with the personnel he has designated as the
   "technical and zone" contacts for his domain, for many administrative
   decisions will be made on the basis of input from these people.


   A zone consists of those contiguous parts of the domain tree for
   which a domain server has complete information and over which it has
   authority.  A domain server may be authoratative for more than one
   zone.  The domain technical/zone contact is the person who tends to
   the technical aspects of maintaining the domain's name server and
   resolver software, and database files.  He keeps the name server
   running, and interacts with technical people in other domains and
   zones to solve problems that affect his zone.


   Domain or host name choices and the allocation of domain name space
   are considered to be local matters.  In the event of conflicts, it is
   the policy of the NIC not to get involved in local disputes or in the
   local decision-making process.  The NIC will not act as referee in
   disputes over such matters as who has the "right" to register a
   particular top-level or second-level domain for an organization.  The
Show full document text