---------------------------------------------------------------------------- Obtaining an Internet Address from NIC Domain Registrar SunFLASH Vol 17 #2 May 1990 ---------------------------------------------------------------------------- This is from USENET . . . >From: DDN Reference Subject: application forms Cc: nic@NIC.DDN.MIL [ NETINFO:DOMAIN-TEMPLATE.TXT ] [ 12/89 ] To establish a domain, the following information must be sent to the NIC Domain Registrar (HOSTMASTER@NIC.DDN.MIL). Questions may be addressed to the NIC Hostmaster by electronic mail at the above address, or by phone at (415) 859-3695 or (800) 235-3155. 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, etc...) 1. Top-level name: (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 geographical address of the organization establishing the domain. 3a. Geographical address: 3b. Organization name: (4) If applicable, the date you expect the fully qualified domain name to begin appearing in HOSTS.TXT. 4. Date operational: Please note: Registration of a domain does not imply an automatic name change to previously registered ARPANET or MILNET hosts that will be included in the domain. Please list below the official host names and network addresses of any ARPANET or MILNET hosts that now appear in HOSTS.TXT whose names will change as a result of this domain registration. (Also be sure to answer question #10, below.) (5) The NIC handle of the administrative head of the organization. Alternately, the person's name, title, 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. Administrative Contact 5a. NIC Handle (if known) : 5b. Name (Last, First) : 5c. Title : 5d. Organization: 5e. Mail Address: 5f. Phone Number: 5g. Net Mailbox : (6) The NIC handle of the technical contact for the domain. Alternately, the person's name, title, 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. Title : 6d. Organization: 6e. Mail Address: 6f. Phone Number: 6g. Net Mailbox : (7) Domains must provide at least two independent servers on connected networks that provide the domain service for translating names to addresses for hosts in this domain. Establishing the servers in physically separate locations and on different PSNs and/or networks is strongly recommended. A description of the primary and secondary server machines, including - Host domain name and network addresses - Any domain-style nicknames (please limit your domain-style nickname request, if any, to one) - Hardware and software, using keywords from the Assigned Numbers RFC. Primary Server: HOST-DOMAIN-NAME, NETADDRRESS, HARDWARE, SOFTWARE 7a. Primary Server Name: 7b. Primary Server Netaddress: 7c. Primary Server Hardware: 7d. Primary Server Software: (8) The Secondary server information. 8a. Secondary Server Name: 8b. Secondary Server Netaddress: 8c. Secondary Server Hardware: 8d. Secondary Server Software: (9) A description of the servers that provide the domain service and the date they will be operational. 9. Description and date operational: (10) Planned mapping of names of any other network hosts (including any ARPANET or MILNET hosts), other than the server machines, into the new domain's naming space. For example: BAR-FOO2.ARPA (10.8.0.193) -> FOO2.BAR.COM BAR-FOO3.ARPA (10.7.0.193) -> FOO3.BAR.COM BAR-FOO4.ARPA (10.6.0.193) -> FOO4.BAR.COM (11) 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 10 WORKING DAYS FOR PROCESSING THIS APPLICATION For further information contact the DDN/ARPANET Network Information Center (NIC): Via electronic mail: HOSTMASTER@NIC.DDN.MIL Via telephone: (800) 235-3155 Via postal mail: SRI International DDN Network Information Center 333 Ravenswood Avenue EJ286 Menlo Park, CA 94025 RECOMMENDED READING (available from the NIC) 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 [ NETINFO:USER-TEMPLATE.TXT ] [ 6/88, SS ] PROCEDURE FOR MILNET/ARPANET REGISTRATION This file contains information for registering individual users in the official MILNET/ARPANET User Registration (WHOIS) Database which is maintained by the DDN Network Information Center (DDN NIC) on SRI-NIC. A user registration template has been created to standardize the registration procedure and guarantee that the DDN NIC will receive complete information about each user. This file contains instructions for filling in the User Registration template, instructions for sending the template to the DDN NIC, a sample template, and a blank template. I. GUIDELINES AS TO WHO MAY BE A REGISTERED USER OF THE MILNET/ARPANET Any MILNET or ARPANET user with a valid account on a network host may be included in the NIC WHOIS Database. Users of the network should be engaged in U.S. government business or research, or should be actively involved in providing operations or system support for government-owned or government-supported MILNET/ARPANET computer communications equipment. II. HOW TO FILL IN THE USER REGISTRATION TEMPLATE Using an editor of your choice, create a file containing the blank template and fill in all relevant fields. Each field should begin on a new line. Detailed instructions for filling out the template are given below under SPECIFIC INSTRUCTIONS FOR EACH FIELD. 214 III. USERS REQUESTING ACCESS TO MILNET TACS If you require TAC access, please contact your Host Administrator. You can determine the name and network mailbox of your Host Administrator by consulting the files NETINFO:MIL-HOST-ADMINISTRATORS-A-L.TXT NETINFO:MIL-HOST-ADMINISTRATORS-M-Z.TXT NETINFO:ARPA-HOST-ADMINISTRATORS.TXT on the SRI-NIC machine. These files can be FTPed to your host. Alternatively, you may access the WHOIS/NICNAME Server to receive host information online, including the name and network mailbox of your Host Administrator, by executing the command: WHOIS HOSTNAME (where "hostname" is the name of your host) IV. WHERE TO SEND THE COMPLETED TEMPLATE The completed template should be sent to REGISTRAR@NIC.DDN.MIL. V. SPECIFIC INSTRUCTIONS FOR EACH TEMPLATE FIELD FULL NAME: The name may be entered in any of the following formats: Lastname, Firstname I. Lastname, Firstname Lastname, I. Middlename Lastname, Firstname I., Jr. Lastname, Firstname I., III where "I." = an initial Do not include military rank or professional titles. U.S. MAIL ADDRESS - some standard procedures: Line 1: The name of your organization; do not use acronyms. Line 2: Information such as the department name, code, or attention line. Line 3: (optional) The building name or number, room number). Line 4: Your street address or Post Office Box. Line 5: City, state and zip code. If you commonly use a 9 digit zip code, enter that. DO NOT USE ANY ABBREVIATIONS OR ACRONYMS, with the exception of Incorporated.......Inc. Limited............Ltd. Corporation........Corp. Company............Co. Post Office Box....P.O. Box Separate lines of the address by a carriage return. PHONE: Up to four phone numbers are allowed. Acceptable formats are: U.S. numbers (123) 456-7890 (123) 456-7890 ext 123 (123) 456-7890 (DSN) 567-7890 (123) 456-7890 (DSN) 567-7890 (FTS) 667-7890 (123) 456-7890 or 456-0987 (DSN) 567-7890 or 567-0987 Overseas numbers [49] 711-123456 or (DSN) 420-1234 or (M) 8765-1234 (For overseas numbers, specify the country code in brackets.) AUTHORIZING HOST: This is the name of the user's "home" host, or on which the user is doing the primary work for which he or she is authorized to use the MILNET or ARPANET. Enter the OFFICIAL HOSTNAME rather than an approved nickname. PRIMARY LOGIN NAME: This is the primary login name/username/directory name of the user on the authorizing host. If the login name is a part of the security system on your host and therefore should be kept secret, do not enter it in this field. The primary login name may be a group directory name if it is the only one the individual uses. PRIMARY NETWORK MAILBOX: This is the mailbox where this individual prefers to receive mail. This may or may not be his or her primary login name on the host. If mail addresses are case dependent on your host, specify the mailbox string accordingly. Otherwise enter the string in upper case. Separate the username and hostname parts of the mailbox by "@". Format: USERNAME@HOSTNAME Example: SMITH@NIC.DDN.MIL For those hosts whose official hostname is a Fully Qualified Domain Name (FQDN), enter the FQDN in the hostname part of the mailbox. The FQDN is preferred. Example: Smith@AI.AI.MIT.EDU TERMINATION DATE: The DEROS date (Date Eligible for Return from Overseas) for military users, estimated date of graduation for students, estimated elapse date for temporary users. This field was requested for use on military hosts. Others may use the field if they wish. Format: MO/YR Example: 10/87 ======================================================================= SAMPLE USER REGISTRATION TEMPLATE ======================================================================= FULL NAME: Kahn, Susan U.S. MAIL ADDRESS: SRI International Telecommunication Sciences Center Network Information Center 333 Ravenswood Avenue Menlo Park, California 94025 PHONE: (415) 859-6111 AUTHORIZING HOST: SRI-NIC PRIMARY LOGIN NAME: SKAHN PRIMARY NETWORK MAILBOX: SKAHN@NIC.DDN.MIL TERMINATION DATE: ======================================================================= USER REGISTRATION TEMPLATE ======================================================================= FULL NAME: U.S. MAIL ADDRESS: PHONE: AUTHORIZING HOST: PRIMARY LOGIN NAME: PRIMARY NETWORK MAILBOX: TERMINATION DATE: ------- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Sunflash is an electronic mail news service from Sun Microsystems, Ft. Lauderdale, FL. Please address comments to FLASH [John McLaughlin] (sun!sunvice!flash or flash@sunvice.East.Sun.COM). (305) 776-7770.