[ NETINFO:DOMAIN-TEMPLATE.TXT ]

  To establish a domain, the following information must be sent to
  the NIC Domain Registrar ([email protected]).  Questions
  may be addressed to the NIC Hostmaster by electronic mail at the
  above address, or by phone at (703) 802-4535 or (800) 365-3642.

  NOTE: The key people must have electronic mailboxes and NIC
  "handles," unique NIC database identifiers.  If you have access to
  "WHOIS", please check to see if you are registered and if so, make
  sure the information is current.  Include only your handle and any
  changes (if any) that need to be made in your entry.  If you do not
  have access to "WHOIS", please provide all the information indicated
  and a NIC handle will be assigned.

  (1) The name of the top-level domain to join
      (EDU, COM, MIL, GOV, NET, ORG).

       1.  Top-level domain:


  (2) The name of the domain (up to 12 characters).  This is the name
  that will be used in tables and lists associating the domain with the
  domain server addresses.  [While, from a technical standpoint, domain
  names can be quite long we recommend the use of shorter, more user-
  friendly names.]

       2.  Complete Domain Name:


  (3) The name and address of the organization establishing the
domain.

       3a.  Organization name:


       3b.  Organization address:



  (4) The date you expect the domain to be fully operational.

       4.  Date operational:



  (5) The NIC handle of the administrative head of the organization --
  or this person's name, mailing address, phone number, organization,
  and network mailbox.  This is the contact point for administrative
  and policy questions about the domain.  In the case of a research
  project, this should be the principal investigator.

  NOTE: Both the Administrative and the Technical/Zone contact of a
  domain MUST have a network mailbox, even if the mailbox is to be
  within the proposed domain.


        Administrative Contact

    5a.  NIC Handle (if known) :
    5b.  Name (Last, First) :
    5c.  Organization:
    5d.  Mail Address:

    5e.  Phone Number:
    5f.  Net Mailbox :


  (6) The NIC handle of the technical contact for the domain -- or
  the person's name, mailing address, phone number, organization,
  and network mailbox.  This is the contact point for
  problems concerning the domain or zone, as well as for updating
  information about the domain or zone.

        Technical and Zone Contact

    6a.  NIC Handle (if known):
    6b.  Name (Last, First) :
    6c.  Organization:
    6d.  Mail Address:


    6e.  Phone Number:
    6f.  Net Mailbox :


  (7) Domains must provide at least two independent servers
      on Government-sponsored networks that provide the domain
      service for translating names to addresses for hosts in
      this domain.

  * If you are applying for a domain and a network number assignment
  simultaneously and a host on your proposed network will be used
  as a server for the domain, you must wait until you receive your
  network number assigment and have given the server(s) a netaddress
  before sending in the domain application.  Sending in the domain
  application without complete information in Sections 7 and 8 of
  this template will result in the delay of the domain registration.

  Also, establishing the servers in physically separate locations
  and on different PSNs and/or networks is strongly recommended.

  NOTE: All new hosts acting as servers will appear in the DNS root
        servers but will not apppear in the HOSTS.TXT file
        unless otherwise requested.

     Primary Server: HOSTNAME, NETADDRESS, HARDWARE, SOFTWARE

     7a.  Primary Server Hostname:
     7b.  Primary Server Netaddress:
     7c.  Primary Server Hardware:
     7d.  Primary Server Software:


  (8) The Secondary server information.

     8a.  Secondary Server Hostname:
     8b.  Secondary Server Netaddress:
     8c.  Secondary Server Hardware:
     8d.  Secondary Server Software:


  (9) If any currently registered hosts will be renamed into the new
      domain, please specify old hostname, netaddress, and new hostname.

     For example:

        BAR-FOO2.XYZ.COM (26.8.0.193) -> FOO2.BAR.COM
        BAR-FOO3.XYZ.COM (192.7.3.193) -> FOO3.BAR.COM
        BAR-FOO4.ARPA (34.6.0.193) -> FOO4.BAR.COM

     NOTE: Hostname changes to MILNET hosts must be approved by the
            MILNET Manager - [email protected].


  (10) Please describe your organization briefly.

     For example: Our Corporation is a consulting
     organization of people working with UNIX and the C language in an
     electronic networking environment.  It sponsors two technical
     conferences annually and distributes a bimonthly newsletter.


PLEASE ALLOW AT LEAST 8 WORKING DAYS FOR PROCESSING THIS APPLICATION

For further information contact the DDN/INTERNET Network Information
Center (NIC):

     Via electronic mail:  [email protected]
     Via telephone:        (800) 365-3642 or (703) 802-4535
     Via postal mail:      DDN Network Information Center
                           14200 Park Meadow Dr., Suite 200
                           Chantilly, VA  22021



             RECOMMENDED READING (available from the NIC)

Feinler, E.J.; Jacobsen, O.J.; Stahl, M.K.; Ward, C.A., eds.  DDN
 Protocol Handbook: Menlo Park, CA: SRI International, DDN Network
 Information Center; 1985 December; NIC 50004 and NIC 50005 and NIC
 50006. 2749 p.

Garcia-Luna-Aceves, J.J.; Stahl, M.K.; Ward, C.A., eds.  Internet
 Protocol Handbook: The Domain Name System (DNS) Handbook. Menlo Park,
 CA: SRI International, Network Information Systems Center; 1989
 August; 219 p. AD A214 698.

Postel, J.B.; Reynolds, J.K.  Domain Requirements. Marina del Rey, CA:
 University of Southern California, Information Sciences Inst.; 1984
 October; RFC 920. 14 p. (NIC.DDN.MIL  RFC:RFC920.TXT).

Harrenstien, K.; Stahl, M.K.; Feinler, E.J.  DoD Internet Host Table
 Specification. Menlo Park, CA: SRI International, DDN Network
 Information Center; 1985 October; RFC 952. 6 p. (NIC.DDN.MIL
   RFC:RFC952.TXT).  Obsoletes: RFC 810

Harrenstien, K.; Stahl, M.K.; Feinler, E.J.  Hostname Server. Menlo
 Park, CA: SRI International, DDN Network Information Center; 1985
 October; RFC 953. 5 p. (NIC.DDN.MIL  RFC:RFC953.TXT).
   Obsoletes: RFC 811

Partridge, C.  Mail Routing and the Domain System. Cambridge, MA: BBN
 Labs., Inc.; 1986 January; RFC 974. 7 p. (NIC.DDN.MIL
   RFC:RFC974.TXT).

Lazear, W.D.  MILNET Name Domain Transition. McLean, VA: MITRE Corp.;
 1987 November; RFC 1031. 10 p. (NIC.DDN.MIL  RFC:RFC1031.TXT).

Stahl, M.K.  Domain Administrators Guide. Menlo Park, CA: SRI
 International, DDN Network Information Center; 1987 November; RFC
 1032. 14 p. (NIC.DDN.MIL  RFC:RFC1032.TXT).

Lottor, M.  Domain Administrators Operations Guide. Menlo Park, CA:
 SRI International, DDN Network Information Center; 1987 November; RFC
 1033. 22 p. (NIC.DDN.MIL  RFC:RFC1033.TXT).

Mockapetris, P.  Domain Names - Concepts and Facilities. Marina del
 Rey, CA: University of Southern California, Information Sciences
 Inst.; 1987 November; RFC 1034. 55 p. (NIC.DDN.MIL
   RFC:RFC1034.TXT).  Updated-by: RFC 1101
   Obsoletes: RFC 973; RFC 882; RFC 883

Mockapetris, P.  Domain names - Implementation and Specification.
 Marina del Rey, CA: University of Southern California, Information
 Sciences Inst.; 1987 November; RFC 1035. 55 p. (NIC.DDN.MIL
   RFC:RFC1035.TXT).  Updated-by: RFC 1101
   Obsoletes: RFC 973; RFC 882; RFC 883

Mockapetris, P.  DNS Encoding of Network Names and Other Types. Marina
 del Rey, CA: University of Southern California, Information Sciences
 Inst.; 1989 April; RFC 1101. 14 p. (NIC.DDN.MIL  RFC:RFC1101.TXT).
   Updates: RFC 1034; RFC 1035


Downloaded From P-80 International Information Systems 304-744-2253

You are viewing proxied material from infinitelyremote.com. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.