[This domain application is for organizations which wish to have UUNET provide name service. Individuals, public access systems, and others not represented by an organization may wish to register in the US domain (contact us-domain-request@isi.edu). ] BACKGROUND: A "zone" is a registry of domains kept by a particular organization. A zone registry is "authoritative", that is, the master copy of the registry is kept by the zone organization, and this copy is, by definition, always up-to-date. Copies of this registry may be distributed to other places and kept in caches, but these caches are not authoritative because they may be out of date. An authoritative answer is required for certain decisions, such as "this mail cannot be delivered because there is no such domain", or "the name you have chosen is available and is now assigned uniquely to you." You need a registered domain name to use software (including smail) which supports domain addresses. This name must be unique in the world, and must be registered with the appropriate registry. You also need to be in a domain that has a forwarder from the internet. Currently, the domain tree in the USA has three major top level domains: COM for companies, EDU for educational institutions, and GOV for government entities. Three other top level names, MIL, NET, and ORG, exits but are somewhat specialized. For the most part, countries other than the USA are using the ISO 3166 2 letter abbreviation for their country as a top level. The top-level domain US fits in this group. The second level is generally the name of the organization, using the shortest possible abbreviation that is clear and unique, thus ATT, DEC, IBM, HP, etc. The choice of exact name is up to the organization, and longer names, such as Berkeley.EDU or Tektronix.COM are perfectly acceptable. Just remember that people must type the name, as well as see it displayed. Only the second level domain name need be registered. Not all countries use the second level for the organization. In particular, Australia and Britain have set up second level domains OZ.AU and AC.UK for their academic communities, and put the organization at the third level. In the US domain, the second and third levels are used for the state and city/county respectively. The third and subsequent levels, if used, should be organizational units within the organization. Try to keep the number of levels to a minimum, since people have to type the names. More than four total levels (country, org, org-unit1, and org-unit2) should rarely be needed. The actual organizational units to be used are up to you, for example, they might be departments, or they might be machine names. You do not need to register levels beneath the second level. CHOSING NAMES: Domain names are case independent. uucpnames MUST be all lower case. "vax", "u3b20", and the like are terrible host names, because sooner or later you'll have more than one vax, or more than one 3b20, and the names will be confusing. We recommend organizational names, with any subdomains based on the department or project the machine is used for. We highly discourage use of a nonorganizational second-level domain name. Uucpnames, product names, and other names which don't represent your entire organization are not good choices. Of course, in order to keep the names reasonably short and to avoid duplicating names in the heirarchy, some compromise will be needed. For example, csvax.CS.UND.EDU is redundant, but RISC.CS.UND.EDU might be a good name for the computer used by the RISC project in the CS department. Please note that you should support both RFC 976 and the documents it refers to, in particular RFC 822 and RFC 920. This means, for example: (a) The name "postmaster" on all machines visible to the outside should be forwarded to the technical contact. This can be easily done with an alias in /usr/lib/aliases, if your site runs sendmail or smail release 2.0 or beyond. (b) Your machine should not alter valid RFC 822 headers, such as From:, of mail it generates or forwards. Many machines running sendmail have a bug which adds uucpname! to the front of such addresses. Installing smail will fix the bug, because mail passed through the machine is not passed through sendmail. We hope to make a fix to sendmail available, also, at a later date. REGISTRATION COSTS: UUNET charges a one time fee of $50 for processing the forms and setting up the servers. This fee does NOT include a connection to the uunet computer. Current UUNET subscribers may register a domain for their organization at no charge. Payment should be sent to: UUNET Technologies, Inc. 3110 Fairview Park Drive, Suite 570 Falls Church, VA 22042 +1 703 204 8000 uunet!domain-request Please indicate the name of your domain (eg: FOO.COM) on your payment so that we may properly credit you. Except for UUNET subscribers, registration can not be completed until payment is received. We recommend that you send payment at the time you email the form. We can not invoice for payment of domain registrations. Information about UUNET's other services can be obtained by sending your postal address to uunet!info IMPLEMENTATION DETAILS: We will notify you via mail to "postmaster" in your domain when your domain is registered. Please make sure such an address exists in your domain. You can NOT use your domain name in outgoing mail until registration is completed, although it is OK to install smail (using the host.UUCP domain) ahead of time. We do recommend that you set up to accept incoming mail for your domain name ahead of time, if this is convenient. UUNET does not provide technical support for configuration of domains and the associated software. Several steps are needed before your registration is complete. Some of these steps are approval by the NIC, setting up the nameservers, and setting up the forwarder. Seeing your domain published in the UUCP map is not, by itself, sufficient (or necessary) for the use of your domain name. FORWARDERS: A forwarder is a kind of mail bridge host between the Internet (formerly called the ARPANET) and UUCP. The nameserver structure directs all Internet mail for your domain to the forwarder, and the forwarder passes the mail from Internet into UUCP. Forwarders can also forward your mail from UUCP to Internet, but it is not strictly necessary to use your forwarder for this, since mail to any of the published UUCP->Internet gateways can do this. If you use a forwarder other than uunet you must have the postmaster or a system administrator at the forwarder send uunet a message granting permission to use their system as a forwarder. UUNET will not contact forwarders to find out if they're willing to forward for you. To register your domain, you need to have a forwarder. If you know of an Internet site (such as uunet) that is willing to be a forwarder for your domain, let us know. As a last resort, uunet can be a forwarder for you even if you are not directly connected. HOWEVER, we require that you have the postmaster or system administrator at the site that is directly connected to uunet and will route your mail send uunet a message of permission before we start forwarding mail through them. THE APPLICATION: To register your domain with the NIC, we need to send in the following form. Questions 4,7,8 and 9 are already answered for you. Do NOT change them. Answer questions 0,1,2,3,5,6 and 10 and return THE ENTIRE FORM (the text within, and including, the bracketed START/END lines) to uunet!domain-request. PLEASE do not just return the questions you answer and do not reformat the application. It creates extra work for us as we have to copy your answers back onto the form we originally sent you, and this will delay your registration. [ THE FORM STARTS HERE. ] (0a) Specify what machine you want to be your forwarder. If you are directly connected to uunet, uunet can be your forwarder. If you are not directly connected, then you need to find some other site to be your forwarder OR get the permission of a site that IS directly connected to uunet to allow your arpanet mail to be forwarded through them. We must receive the permission of the uunet site or the other forwarder directly from that forwarder. Who will be your forwarder: For Example: uunet.uu.net (0b) Specify the uucpname registered in the UUCP maps of the system which will act as the mail gateway for your domain. This is optional, but highly recommended, for domains which do not use uunet.uu.net as forwarder. UUNET subscribers using uunet.uu.net as forwarder may simply give the name of the account. What is the name of your mail gateway: [ NETINFO:DOMAIN-TEMPLATE.TXT ] [ 10/90 DM ] 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 (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: Now 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 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: ns.UU.NET 7b. Primary Server Netaddress: 137.39.1.3 7c. Primary Server Hardware: SUN-4/65 7d. Primary Server Software: UNIX (8) The Secondary server information. 8a. Secondary Server Hostname: uucp-gw-1.pa.DEC.COM 8b. Secondary Server Netaddress: 16.1.0.18 8c. Secondary Server Hardware: DEC 8d. Secondary Server Software: UNIX 8a. Secondary Server Hostname: uucp-gw-2.pa.DEC.COM 8b. Secondary Server Netaddress: 16.1.0.19 8c. Secondary Server Hardware: DEC 8d. Secondary Server Software: UNIX 8a. Secondary Server Hostname: ns.EU.NET 8b. Secondary Server Netaddress: 192.16.202.11 8c. Secondary Server Hardware: SUN-4/280 8d. Secondary Server Software: UNIX 8a. Secondary Server Hostname: ns1.RUTGERS.EDU 8b. Secondary Server Netaddress: 128.6.21.6 8c. Secondary Server Hardware: Sun-4/60 8d. Secondary Server Software: UNIX (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 - MILNETMGR@DDN-CONUS.DDN.MIL. (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 30 WORKING DAYS FOR PROCESSING THIS APPLICATION [ THE FORM ENDS HERE. ] For further information contact the DDN/INTERNET Network Information Center (NIC): Via electronic mail: HOSTMASTER@NIC.DDN.MIL 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