To establish a domain within the DOM-JM, the following information must be sent to the JAMNet Registration Services (DOMAINMASTER@ns.jm). Either this template, or the "short form" following this template may be used. (1) The name of the top-level domain to join (EDU, GOV, COM, NET, ORG). 1. Top-level domain: com (2) The name of the domain (up to 24 characters). This is the name that will be used in tables and lists associating the domain with the domain servers addresses. While domain names can be quite long, the use of shorter, more user-friendly names is recommended. 2. Complete Domain Name: (3) The name and address of the organization for which the domain is being established. 3a. Organization name: 3b. Organization address: (4) The date you expect the domain to be fully operational. 4. Date operational: NOTE: The key people must have electronic mailboxes (even if in the domain being registered). (5) The handle of the administrative head of the organization in (3) above or this person's name, postal address, phone number, organization, and network emailbox. This is the contact point for administrative and policy questions about the domain. Administrative Contact 5a. Handle (if known): 5b. Name (Last, First): 5c. Organization: 5d. Postal Address: 5e. Phone Number: 5f. Net Mailbox: (6) The handle of the technical contact for the domain or this person's name, mailing address, phone number, organization, and network mailbox. This is the contact point for problems and updates regarding the domain or zone. Technical and Zone Contact 6a. Handle (if known): 6b. Name (Last, First): 6c. Organization: 6d. Postal Address: 6e. Phone Number: 6f. Net Mailbox: NOTE: Domains must provide at least two independent servers for translating names to addresses for hosts in the domain. The servers should be in physically separate locations and on different networks if possible. The servers should be active and responsive to DNS queries BEFORE this application is submitted. Incomplete information in sections 7 and 8 or inactive servers will result in delay of the registration. (7) The primary server information. 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) Please briefly describe the organization for which this domain is being registered. If the domain is for an organization that already has a domain registered, please describe the purpose of this domain. Rolex is a big Watch manufacturer. We are requesting the registration of rolex.com.jm for webadvertising and trademark purposes. For further information contact Via electronic mail: DOMAINMASTER@ns.jm Via telephone: (809) 927-2148 The party requesting registration of this name certifies that, to her/his knowledge, the use of this name does not violate trademark or other statutes. Registering a domain name does not confer any legal rights to that name and any disputes between parties over the rights to use a particular name are to be settled between the contending parties using normal legal methods. (See RFC 1591)  1. Top-level domain.....: 2. Complete Domain Name.: 3a. Organization name....: 3b. Organization address.: 4. Operational Date.....: Administrative Contact: 5a. Handle (if known): 5b. Name (Last, First): 5c. Organization: 5d. Postal Address: 5e. Phone Number: 5f. Net Mailbox: Technical/Zone Contact: 6a. Handle (if known): 6b. Name (Last, First): 6c. Organization: 6d. Postal Address: 6e. Phone Number: 6f. Net Mailbox: 7a. Prime Server Hostname...: 7b. Prime Server Netaddress.: 7c. Prime Server Hardware...: 7d. Prime Server Software...: 8a. Second Server Hostname..: 8b. Second Server Netaddress: 8c. Second Server Hardware..: 8d. Second Server Software..: 9. Domain/Org Purpose/Desc.: Notes: In Sections 3b, 5d, & 6d use multiple lines for addresses. If contacts are registered, only 5a and 6a are needed. If servers are registered, only 7a&b and 8a&b are needed. If there is more than one secondary server, just copy Section 8. The party requesting registration of this name certifies that, to her/his knowledge, the use of this name does not violate trademark or other statues. Registering a domain name does not confer any legal rights to that name and any disputes between parties over the rights to use a particular name are to be settled between the contending parties using normal legal methods. (See RFC 1591)  RECOMMENDED READING Albitz, P., C. Liu, "DNS and Bind" Help for UNIX System Administrators, O'Reilly and Associates, Inc., October 1992. Postel, J., "Domain Name System Structure and Delegation". Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1994 March; RFC 1591. 7 p. Cooper, Postel, "The US Domain". Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1992 December; RFC 1480. 31 p. Stahl, M.K. Domain Administrators Guide. Menlo Park, CA: SRI International, DDN Network Information Center; 1987 November; RFC 1032. 14 p. (.internic.net:policy/rfc1032.txt> Lottor, M. Domain Administrators Operations Guide. Menlo Park, CA: SRI International, DDN Network Information Center; 1987 November; RFC 1033. 22 p. Mockapetris, P. Domain Names - Concepts and Facilities. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1987 November; RFC 1034. 55 p. Mockapetris, P. Domain names - Implementation and Specification. Marina del Rey, CA: University of Southern California, Information Sciences Inst.; 1987 November; RFC 1035. 55 p. 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.