Acorn User 4

home *** CD-ROM | disk | FTP | other *** search

/ Acorn User 4 / AUCD4.iso / acorn / documents / appnotes / 261-275 / 265c.arc / Disc / Documents / InterNIC < prev next >

Wrap

Text File | 1996-02-14 | 20.2 KB | 495 lines

[ URL ftp://rs.internic.net/templates/domain-template.txt ] [ 09/95 ] ******************* Please DO NOT REMOVE Version Number ******************** Domain Version Number: 2.0 **************** Please see attached detailed instructions ***************** ******** Only for registrations under ROOT, COM, ORG, NET, EDU, GOV ******** 0. (N)ew (M)odify (D)elete....: 1. Purpose/Description........: 2. Complete Domain Name.......: Organization Using Domain Name 3a. Organization Name..........: 3b. Street Address.............: 3c. City.......................: 3d. State......................: 3e. Postal Code................: 3f. Country....................: Administrative Contact 4a. NIC Handle (if known)......: 4b. Name (Last, First).........: 4c. Organization Name..........: 4d. Street Address.............: 4e. City.......................: 4f. State......................: 4g. Postal Code................: 4h. Country....................: 4i. Phone Number...............: 4j. E-Mailbox..................: Technical Contact 5a. NIC Handle (if known)......: 5b. Name (Last, First).........: 5c. Organization Name..........: 5d. Street Address.............: 5e. City.......................: 5f. State......................: 5g. Postal Code................: 5h. Country....................: 5i. Phone Number...............: 5j. E-Mailbox..................: Billing Contact 6a. NIC Handle (if known)......: 6b. Name (Last, First).........: 6c. Organization Name..........: 6d. Street Address.............: 6e. City.......................: 6f. State......................: 6g. Postal Code................: 6h. Country....................: 6i. Phone Number...............: 6j. E-Mailbox..................: Primary Name Server 7a. Primary Server Hostname....: 7b. Primary Server Netaddress..: Secondary Name Server(s) 8a. Secondary Server Hostname..: 8b. Secondary Server Netaddress: Invoice Delivery 9. (E)mail (P)ostal...........: A domain name registration fee of $100.00 US is applicable. This charge will cover the $50.00 maintenance fee for two (2) years. After the two year period, an invoice will be sent on an annual basis. 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). By applying for the domain name and through the use or continued use of the domain name, the applicant agrees to be bound by the terms of NSI's then current domain name policy (the 'Policy Statement') which is available at ftp://rs.internic.net/policy/internic.domain.policy. (If this application is made through an agent, such as an Internet Service Provider, that agent accepts the responsibility to notify the applicant of the conditions on the registration of the domain name and to provide the applicant a copy of the current version of the Policy Statement, if so requested by the applicant.) The applicant acknowledges and agrees that NSI may change the terms and conditions of the Policy Statement from time to time as provided in the Policy Statement. The applicant agrees that if the use of the domain name is challenged by any third party, or if any dispute arises under this Registration Agreement, as amended, the applicant will abide by the procedures specified in the Policy Statement. This Registration Agreement shall be governed in all respects by and construed in accordance with the laws of the United States of America and of the State of California, without respect to its conflict of law rules. This Registration Agreement is the complete and exclusive agreement of the applicant and NSI ("parties") regarding domain names. It supersedes, and its terms govern, all prior proposals, agreements, or other communications between the parties. This Registration Agreement may only be amended as provided in the Policy Statement. --------------------------------- cut here --------------------------------- GENERAL INSTRUCTIONS Use the form above for registering new domain names, for making changes to existing domain name records and for removing a domain name from the InterNIC database and root servers. The form, and only the form, should be sent via e-mail to HOSTMASTER@INTERNIC.NET Please do not send hardcopy registrations to the InterNIC. Your provider will be able to send e-mail applications if you are not connected. In the Subject of the message, use the words, "NEW DOMAIN", "MODIFY DOMAIN", or "REMOVE DOMAIN" as appropriate, followed by the name of the domain to assist in sorting and locating incoming registration requests. In response to the submission of a form, you should receive an auto-reply with a tracking number. Use the number in the Subject of any messages you send regarding that registration action. When the registration is completed you will receive a notification via e-mail. If you regularly submit domain applications, you will note three changes in the registration form. Section 4 has been removed. We assume that the domain will essentially be operational when the template is submitted and have found the "operational date" to be of little use. Removal of Section 4 moves the Administrative and Technical Contact sections to Section 4 and 5 respectively. A Billing Contact section was added as Section 6, so that invoices and other billing information can be sent to the Billing Contact. Finally, additional fields have been added to the parts of the form that deal with addresses. Street Address, City, State, Postal Code and Country MUST be placed in separate fields. Please do not modify the form nor remove the version number. The computer program that scans and parses the form is looking for section numbers, followed by a period, followed by a colon. Information following the colon is compared with and inserted into the database as appropriate. Please send only one form per message. When completing the form, make use of "whois" at rs.internic.net to check to see if the domain name, organization name, people, and name servers have been registered. Use the information in the database where appropriate. This will minimize the number of registrations that are returned for incomplete or inaccurate information. The instructions for completing each field are in the following three sections - one each for NEW, MODIFY and DELETE. The interpretation of missing or blank fields can vary between the New and Modify registration actions. Please read the instructions carefully and make sure the form is properly completed to accomplish the action you desire. The information on billing of domains and invoices is available at ftp://rs.internic.net/billing/README REGISTERING A NEW DOMAIN NAME Section 0 - Registration Action Type Following the colon, place the character "N" or the word "NEW" to indicate a NEW domain registration. Changing a name from DOMAINAME1 to DOMAINAME2 is treated as a New registration. The transfer of a name from one organization to another is also treated as a New registration. If the intent is to effect a transfer from one organization to another, clearly indicate this in Section 1 and include a statement from the current holder of the name that it is being transferred. Section 1 - Purpose of Registration Briefly describe the organization and/or the purpose for which this domain name is being registered. The description should support the choice of top-level domain in Section 2. If the domain name is for an organization that already has a domain name registered, describe the purpose of this domain and why the additional name is needed. Indicate why existing names cannot be used or why the proposed second- level name cannot be used as a third-level name under a domain name that is already registered. Section 2 - Complete Domain Name Top-level country domains may be registered by inserting the two-letter country code in this section. See RFC1591 for the duties and responsibilities of top-level domain administrators. For second-level domain names under COM, ORG, NET, EDU, GOV insert the two-part name of the domain you wish to register, for example, ABC.COM. The total length of the two-part name may be up to 24 characters. The only characters allowed in a domain name are letters, digits and the dash (-). A domain name cannot begin or end with a dash (see RFC952). Consult RFC1591 to determine the most appropriate top-level domain to join. Briefly: COM is for commercial, for-profit organizations ORG is for miscellaneous usually non-profit organizations NET is for network infrastructure machines and organizations EDU is for 4-year, degree granting institutions GOV is for United States federal government agencies US state and local government agencies, schools, libraries, museums, and individuals should register under the US domain. See RFC1480 for a complete description of the US domain and registration procedures. GOV registrations are limited to top-level US Federal Government agencies (see RFC1816). Section 3 - Organization using the Domain Name The domain name is considered to be registered to an organization, even if the "organization" is an individual. It is important in this section to list the name and address of the end-user organization, not the provider organization. If the organization has the same name as one that is already registered, explain this in Section 1 above. Item 3b may be copied as many times as necessary to reflect different lines of the Street Address. If item 3c, 3d or 3e is not applicable for your country, leave that item blank. Section 4 - Administrative Contact The administrative contact is the person who can speak on behalf of the organization listed in Section 3. This person should be able to answer non-technical questions about the organization's plans for the name, and procedures for establishing sub-domains, and should be able to represent the organization regarding use of the name. See RFC1032 for more detail on administrative contacts. Each person in the InterNIC database is assigned a "handle" - a unique tag consisting of the person's initials and a serial number. This tag is used on records in the database to indicate a point of contact for a domain name, network, name server or other entity. Each person should have only one handle. If the person's handle is known, insert just the handle in item 4a and leave the rest of Section 4 blank. If a person's handle is unknown or the person has never been registered, leave item 4a blank. The registration software will check for an existing user record. If a matching user record is found, the record will be updated with any new information contained in the template. All contacts MUST include information in items 4i and 4j. Templates that do not have this information will be returned. Section 5 - Technical Contact The technical contact is the person who tends to the technical aspects of maintaining the domain's name server, resolver software, and database files. This person keeps the name server running, and interacts with technical people in other domains to solve problems that affect the domain. The Internet Service Provider often performs this role. The procedures for completing Section 5 are the same as those for Section 4. If Section 5 is left blank, the information from Section 4 will be assumed and vice-versa. Section 6 - Billing Contact The billing contact will be sent invoices for new domain registrations and re-registrations. The procedures for completing Section 6 are the same as those for Section 4. If Section 6 is left blank, the information from Section 4 will be assumed. Section 7 - Primary Name Server 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. The registration software makes a cross check between the host name given and the IP addresses given to see if there are matches with either in the database. If a match with an IP number in the database is found, the name in the database will be assumed. Neither the name nor number of a registered name server will be changed as a result of a new domain registration. A Modify registration request MUST be sent to change either of these values. Please provide the fully-qualified name of the machine that is to be the name server; for example: "machine.domainame.com" not just "machine" Section 8 - Secondary Name Server(s) The procedures for completing Section 8 are the same as for Section 7. At least one secondary name server is required. If several secondary servers are desired, copy Section 8 as many times as needed. Please do not renumber or change the copied section. Section 9 - Invoice Delivery If you wish to receive your invoice electronically, place the character "E" or the word "EMAIL" in item 9. If If you wish to receive your invoice by postal mail, place the character "P" or the word "POSTAL" in item 9. MODIFYING A DOMAIN NAME RECORD Changing an existing record is done by replacement. That is, the contents of various fields in the database are replaced with new information from the form. If the modification involves first registering a person or name server that is not in the database, the instructions for completing Sections 4-8 "REGISTERING A NEW DOMAIN NAME" apply. Use "whois" if you are unsure about the current information for a domain, name server, or individual. Changes will be made if it appears that the modification request has come from a "reasonable" source. This source may be from a listed contact for the domain, others in the same organization, the current provider, or a new provider that is about to provide support for the domain. Notification of the change and the approximate time the change will take effect will be sent to: - the requester - if contacts are changing, both old and new contacts - if name servers are changing, the technical contacts for the domains in which the old and new primary name servers reside This dissemination of change information is to ensure that all parties involved are aware and concur with the change. Transfer of a name from one organization to another is considered a new registration. See, "REGISTERING A NEW DOMAIN NAME." Section 0 - Registration Action Type Following the colon, place the character "M" or the word "MODIFY" to indicate a modification to an existing domain registration. Transfer of a name from one organization to another is considered a new registration. See, "REGISTERING A NEW DOMAIN NAME." Section 1 - Purpose of Registration Briefly describe the purpose of the modification. If the intent is to change either the name or the IP address of name servers, make this very clear, otherwise changes to name servers will not be made. If you wish to change the name of the domain itself, file a separate NEW registration and a DELETE registration when you are ready to have the old name removed. Make it clear in this section that you are changing from one domain name to another and estimate how long you will need the old domain name. Section 2 - Complete Domain Name Insert the two-part name of the domain name you wish to modify, for example, ABC.COM. This section MUST be completed, even if you are making minor changes, like the phone number of a point of contact, for example. Section 3 - Organization Using the Domain Name The domain name is considered to be registered to an organization, even if the "organization" is an individual. Therefore, a change in the organization name should be explained in Section 1. Transfer of a domain name from one organization to another is considered a new domain registration. See, "REGISTERING A NEW DOMAIN NAME." Section 4 - Administrative Contact If a handle is given in item 4a, the database will be updated with any information on the form in items 4b through 4j. If any item is missing or blank, the corresponding information in the database will not be altered. If no handle is given, the database will be searched to see if the person is already registered. If so, the person's record will be updated with any new information on the form. If not registered, the person will be entered into the database and assigned a handle. The handle will be attached to the domain name record, thus replacing the old contact with the new one. Both old and new contacts will be notified of the change. Section 5 - Technical Contact The procedures for modifying information in Section 5 are the same as those for Section 4. Section 6 - Billing Contact The procedures for modifying information in Section 6 are the same as those for Section 4. Section 7 - Primary Name Server If any changes in name servers are being made, provide a complete list of name servers (both primary and secondary). The list in the application will replace the list in the database. If the intention is to change the name or IP address of a name server, clearly state that in Section 1 above. The default is to NOT change either of these values unless so instructed in Section 1 and the requester is authorized to do so. Section 8 - Secondary Name Server(s) If any changes in name servers are being made, provide a complete list of name servers (both primary and secondary). The list in the application will replace the list in the database. Section 9 - Invoice Delivery Leave this section blank. DELETING A DOMAIN NAME RECORD A request to remove a registered domain name from the database may come from the administrative or technical contact for the domain or from a provider who is no longer supporting the name. A third party who believes that a domain is inactive and wants to become the holder of the name should NOT submit a Delete form. Instead, a New form should be submitted with a description in Section 1 of attempts to contact the listed domain name holder. When the name is removed, it will no longer be visible via whois, wais, gopher, or Web browsers that query the InterNIC database. It will also be removed from the root name servers on the subsequent update. Notification of the deletion and the approximate time it will take effect will be sent to: - the requester - the contacts currently listed - the technical contact for the domain in which the primary name server resides When a name is transferred from one organization to another, the InterNIC will first delete the existing record and then process a new registration. If an invoice is not paid within the specified time period, the domain name will be automatically deleted. If the domain name has been placed on hold for more than 90 days because of lack of name service, the domain name may be deleted. Section 0 - Registration Action Type Following the colon, place the character "D" or the word "DELETE" to indicate a deletion of an existing domain registration. Section 1 - Purpose of Registration Briefly state the reason for removing the name. If additional records, such as the point(s) of contact or name servers should also be deleted, state that in this section. These will not be automatically removed. The InterNIC will check further to see if they are used on other domain, network, or autonomous system number records before removing them. Section 2 - Complete Domain Name Insert the two-part name of the domain name you wish to have deleted. Section 3 - Organization Using the Domain Name This section MUST be filled completely. Section 4 - Section 9 These sections should be left blank.