[ URL ftp://rs.internic.net/templates/in-addr-template.txt ] [ 06/95 ] **************** Please DO NOT REMOVE Version Number ****************** IN-ADDR Version Number: 1.0 ************* Please see attached detailed instructions *************** Registration Action Type 0. (N)ew (M)odify (D)elete: Network Information 1a. Network Name..................: 1b. Start of Network Block........: 1c. End of Network Block..........: 2a. Name of Organization..........: 2b. Postal address of Organization: Technical Contact 3a. NIC Handle (if known).........: 3b. Name (Last, First)............: 3c. Organization..................: 3d. Postal Address................: 3e. Phone Number..................: 3f. E-Mail Address................: Primary Name Server 4a. Primary Server Hostname.......: 4b. Primary Server Netaddress.....: Secondary Name Server(s) 5a. Secondary Server Hostname.....: 5b. Secondary Server Netaddress...: 6. Comments......................: ------------------------------- cut here --------------------------------- GENERAL INSTRUCTIONS What is an IN-ADDR domain: The Internet uses a special domain to support address to name mapping, referred to as inverse-addressing (IN-ADDR). IN-ADDR domains are represented using the network number in reverse. For example, the IN-ADDR domain for network 123.45.67.0 is represented as 67.45.123.IN-ADDR.ARPA. PLEASE DO NOT LIST YOUR NETWORK NUMBER IN REVERSE ON YOUR TEMPLATE. Use the above template for registering new IN-ADDR entries, making changes to existing IN-ADDR records, and removing inverse-address mapping from the InterNIC database and root servers. This template, and only this template, 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 for you if you are not connected. Please do not modify the template nor remove the version number. PLEASE SEND ONLY ONE TEMPLATE PER MESSAGE. In the Subject of the message, use the words, "NEW IN-ADDR", "MODIFY IN-ADDR", or "REMOVE IN-ADDR" as appropriate. In response to the submission of a template, you should receive an auto-reply with a ticket number. The ticket number format is: NIC-.. Use the ticket number in the Subject of any messages you send regarding that registration action. When the registration has been completed, you will receive notification via e-mail in the form of a reply to the requesting party. All ISPs receiving /16 bits or less (>= 256 Class C's) from the InterNIC will be responsible for maintaining all IN-ADDR.ARPA domain records for their respective customers. The ISP will then be responsible for the maintenance of IN-ADDR.ARPA domain records of all longer prefixes that have been delegated out of that block. The instructions for completing each field are in the following four sections - Registration Action Type, Network Information, Technical Contact and Name Servers. Section 0 - Registration Action Type "N" - New IN-ADDR registration. The letter "N" or the word "New" indicates a NEW registration. "M" - Modify an existing IN-ADDR registration. When "M" is selected, the current records will be replaced with the information listed in the template. Please provide a complete list of name servers in the order that they should appear on the record. If the modification involves first registering a person or name server(s) that are not in the database, the instructions for completing Sections 2, 3, 4 and 5 apply. Use the "WHOIS" database if you are not sure about the current information for a technical point of contact or name server(s). Changes will be made if it appears to the operator that the modification request has come from an authorized source. This source could be from a listed contact for the domain, from others in the same organization, from the current provider, or from a new provider that is about to provide support for the network. "D" - Delete existing IN-ADDRs from record. The default for this option will be to remove IN-ADDRs from the network number or block entry listed. The host entry will still exist in the global host tables. Section 1 - Network Record Information Network Name - THIS IS NOT YOUR DOMAIN NAME. Please supply the network name listed in the network's WHOIS record. Start/End of Network Block - If the network record is a single network, item 1b would be the IP address of the single network and item 1c would be blank. If the network record is a block of networks, item 1b would be the IP address of the start of the network block and item 1c would be the IP address of the end of the network block. If you received a block of IP addresses from your Internet Service Provider, there may already be domain name servers on the larger block of addresses held by the provider. Please query your Internet Service Provider before submitting a request for inverse-addressing. Section 2 - Name and postal address of Organization The network is considered to be registered to an organization, even if the "organization" is an individual. If you are an Internet Service Provider submitting this request on behalf of your client, please use the name and postal address of the organization utilizing the IP address(es). When completing item 2b, place the city, state, and zip code on a separate line. Use a comma to separate the city and state. Do not insert a period following the state abbreviation. For example: Organization address.: Street or PO Box Herndon, VA 22070 If the organization is in a country other than the United States, please include the name of the country on the last line by itself. For example: Organization address.: Street or PO Box Montreal, QC H2S 2C8 Canada Section 3 - Technical Point of Contact The technical point of contact is the person who tends to the technical aspects of maintaining the network's name servers. This person should be able to answer any utilization questions the InterNIC may have. 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 3a AND LEAVE THE REST OF SECTION 3 BLANK. IF THE PERSON'S HANDLE IS UNKNOWN OR THE PERSON HAS NEVER BEEN REGISTERED, LEAVE ITEM 3a BLANK. The user's database record will be updated with any new information on the template. Item 3c refers to the name of the organization with which the technical point of contact is affiliated. Item 3d should be completed following guidelines set forth regarding item 2b. Section 4 - Primary Name Server Networks are required to provide at least two independent servers for translating address to name mapping 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 4 and 5, or inactive servers will result in the return of the registration request. Neither the name nor the number of a registered name server will be changed as a result of a new IN-ADDR 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" or just "domainame.com" Many reverse-authentication programs will not search for the nameserver if only the domain name is listed. It is suggested that the fourth octet of an IP address of a server should be neither 0 nor 255. The remaining 254 numbers in the fourth octet of the IP address are valid. Section 5 - Secondary Name Server(s) The same procedures for specifying primary servers apply as to secondary servers. If several secondary servers are required, copy Section 5 as many times as needed. DO NOT RENUMBER OR CHANGE THE COPIED SECTION. A maximum of six domain name servers may be added to a network record. Section 6 - Comments Please utilize Section 6 for all comments and more detailed updates not covered by template Sections 0 through 5.