GENERAL INSTRUCTIONS Use the above Host Template for registering a new Host, for making changes to existing Host records, and for removing a Host from the InterNIC database. The template, and only the template, should be sent via email to HOSTMASTER@INTERNIC.NET. Please do not send hardcopy registrations to the InterNIC. Your Internet Service Provider (ISP) should be able to send email applications if you are not connected. In the Subject of the message, use words "NEW HOST", "MODIFY HOST", or "DELETE HOST" appropriately, followed by the name of the Host to help sort and locate incoming registration requests. In response to the submission of a template, you should receive an auto-reply with a tracking number. Use the tracking number in the Subject of any subsequent message you send regarding that registration action. When the registration is completed you will receive a notification via email. Please DO NOT modify the template or remove the version number. The software that processes the template looks for an item number, followed by a period, followed by a colon. Information following the colon is compared with and inserted into the database. Please send only one template per message. When completing the template, make use of WHOIS at RS.INTERNIC.NET to check to see if the Host and the Contact have been registered. Use that information where appropriate. The detailed instructions for completing each item for NEW, MODIFY, and DELETE follow. REGISTERING A NEW HOST RECORD Section 0 - Authorization In item 0a, enter N or NEW to register a new Host. Items 0b and 0c should be left blank during the registration of a new Host. The request to create a new Host MUST come from a reasonable source. For example, if a Host NS.EXAMPLE.COM is being registered as a new Host, the registration request MUST come from the current Administrative or Technical Contact of the Domain EXAMPLE.COM. Section 1 - Host Item 1a is the NIC handle of a Host. Leave item 1a blank during the registration of a new Host. Enter the Fully Qualified Domain Name (FQDN) of the Host in item 1b. For example, enter NS.EXAMPLE.COM and not just NS. The only valid characters for a Host name are alphabets, digits, and "-". The maximum length of a Host name is 38 characters, including the Domain name and the top-level Domain. Enter a valid IP address for the Host in item 1c. In the InterNIC database, a particular Host name can be associated with one and only one IP address, and vice versa. If an IP address or a Host name is already registered, it CAN NOT be associated with another Host during a new registration. Each Host MUST have a unique IP address and Host name. Section 2 - Contact The Contact tends to the technical aspects of running the Host as a Domain Name Server. Each Contact in the InterNIC database is assigned a handle - a unique identifier to differentiate it from all other records in the database. Only one handle should exist for each individual or role. If the handle is known, enter it in item 2a and leave the rest of the section blank. If the handle is given and additional information is also provided, only the handle will be used. Any additional information will be ignored. Use handles whenever possible. If the Contact handle is unknown or has never been registered, leave item 2a blank. The registration software will check for matches with existing Contact records. If a Contact record is found in the database that matches the information on the template in a significant way (name, and emailbox or phone), the database information will be assumed. Otherwise, the Contact will be registered. A Contact record CAN NOT be updated while using the Host Template. To update Contact information, use the Contact Template available at: ftp://rs.internic.net/templates/contact-template.txt In item 2b, indicate the type of Contact you are registering. If the Contact is an individual, enter I or INDIVIDUAL. If it is a group or organization where several individuals may be acting in that role, enter R or ROLE. In item 2c, enter the name of the individual or role being registered. If the Contact is an individual, the name should be entered as: LASTNAME, FIRSTNAME MIDDLENAME For example: Smith, John X. If the Contact is a role account, list the name of the role account in item 2c and the name of the organization the role account represents in item 2d. Item 2c is REQUIRED for all Contacts. If the name of the role account is the same as that of the organization, fill in item 2c with that name and leave item 2d blank. At least one line of address information is REQUIRED in item 2e. This address should be the postal mailing address for any correspondence directed to the Contact. Enter the city and the standard two-letter state abbreviation in items 2f and 2g respectively if the Contact is located in the United States. You may add as many lines as necessary for your street address. You may do so by repeating item 2e. For the U.S. addresses, the postal code is REQUIRED in item 2h. Enter the ISO two-letter country code in Item 2i. If no country code is entered, the Contact is assumed to be located in the United States. A list of ISO two-letter country codes is available at: ftp://rs.internic.net/netinfo/iso3166-countrycodes Every Contact is REQUIRED to provide at least one valid phone number in item 2j. For informational purposes, you may supply a fax number in item 2k. A valid Internet email address is REQUIRED for all Contacts in item 2l. Separate the username and hostname parts of the mailbox by an "@" symbol. For example: user@example.com MODIFYING A HOST 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 template. Use WHOIS if you are unsure about the current information for the Host or the Contact. Changes to a Host record will be made if it appears that the modification request has come from a reasonable source. This source may be the Contact of the Host or a listed Contact on the Host's parent Domain record. Notification of the modification and the approximate time it will take effect will be sent to: - the requester - the Contact of the Host if it is being replaced with another Contact - the Administrative and Technical Contacts of the Domain in which the Host resides This notification will help ensure that all parties involved are aware of, and agree with, the change. Section 0 - Authorization In item 0a, enter M or MODIFY to indicate a modification to an existing Host registration. If the Contact of the Host has previously used the Contact Template to specify the use of Pretty Good Privacy (PGP) or encrypted password, the authentication scheme and information associated with it should be listed in items 0b and 0c. These items contain the authorization information for the sender of an update request and help determine if the request is coming from a valid sender. These items are REQUIRED when a Host is being modified. Item 0b is the type of authentication scheme. It can have values MAIL-FROM, CRYPT-PW, or PGP. Item 0c is the authorization information for the selected authentication scheme. As shown by the table below, items 0b and 0c are REQUIRED only when CRYPT-PW is the selected authentication scheme. The different items 0b and 0c combinations are: If Item 0b is Then Item 0c is MAIL-FROM Ignored. The FROM field in the mail header of an update message will be checked to verify the sender. MAIL-FROM is the DEFAULT authentication scheme. CRYPT-PW Cleartext password (the plain text of the encrypted password). PGP Ignored. The sender should sign the entire update message with its secret PGP key and send it in cleartext to the InterNIC. Section 1 - Host Item 1a is the NIC handle of a Host. Item 1a is REQUIRED for MODIFY. Enter the Fully Qualified Domain Name (FQDN) of the Host in item 1b. For example, enter NS.EXAMPLE.COM and not just NS. The only valid characters for a Host name are alphabets, digits, and "-". The maximum length of a Host name is 38 characters, including the Domain name and the top-level Domain. Enter a valid IP address for the Host in item 1c. In the InterNIC database, a particular Host name can be associated with one and only one IP address, and vice versa. If an IP address or a Host name is already registered, it CAN NOT be associated with another Host in a MODIFY request. Each Host MUST have a unique IP address and Host name. Section 2 - Contact The Contact tends to the technical aspects of running the Host as a Domain Name Server. Each Contact in the InterNIC database is assigned a handle - a unique identifier to differentiate it from all other records in the database. Only one handle should exist for each individual or role. If the handle is known, enter it in item 2a and leave the rest of the section blank. If the handle is given and additional information is also provided, only the handle will be used. Any additional information will be ignored. Use handles whenever possible. If the Contact handle is unknown or has never been registered, leave item 2a blank. The registration software will check for matches with existing Contact records. If a Contact record is found in the database that matches the information on the template in a significant way (name, emailbox, phone), the database information will be assumed. Otherwise, the Contact will be registered. A Contact record CAN NOT be updated while using the Host Template. To update Contact information, use the Contact Template available at: ftp://rs.internic.net/templates/contact-template.txt In item 2b, indicate the type of Contact you are registering. If the Contact is an individual, enter I or INDIVIDUAL. If it is a group or organization where several individuals may be acting in that role, enter R or ROLE. In item 2c, enter the name of the individual or role being registered. If the Contact is an individual, the name should be entered as: LASTNAME, FIRSTNAME MIDDLENAME For example: Smith, John X. If the Contact is a role account, list the name of the role account in item 2c and the name of the organization the role account represents in item 2d. Item 2c is REQUIRED for all Contacts. If the name of the role account is the same as that of the organization, fill in item 2c with that name and leave item 2d blank. At least one line of address information is REQUIRED in item 2e. This address should be the postal mailing address for any correspondence directed to the Contact. Enter the city and the standard two-letter state abbreviation in items 2f and 2g respectively if the Contact is located in the United States. You may add as many lines as necessary for your street address. You may do so by repeating item 2e. For the U.S. addresses, the postal code is REQUIRED in item 2h. Enter the ISO two-letter country code in Item 2i. If no country code is entered, the Contact is assumed to be located in the United States. A list of ISO two-letter country codes is available at: ftp://rs.internic.net/netinfo/iso3166-countrycodes Every Contact is REQUIRED to provide at least one valid phone number in item 2j. For informational purposes, you may supply a fax number in item 2k. A valid Internet email address is REQUIRED for all Contacts in item 2l. Separate the username and hostname parts of the mailbox by an "@" symbol. For example: user@example.com DELETING A HOST RECORD A Host record will be removed from the InterNIC database if it appears that the delete request has come from a reasonable source. This source may be the Contact of a Host or a listed Contact on the Host's parent Domain record. When the Host 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 Contact of the Host - the Administrative and Technical Contacts of the Domain in which the Host resides This notification will help ensure that all parties involved are aware of, and agree with, the change. A Host CAN NOT be deleted until all the Domain and Network records that are using the Host are updated. Section 0 - Authorization In item 0a, enter D or DELETE to indicate a deletion of an existing Host registration. If the Contact of the Host has previously used the Contact Template to specify the use of Pretty Good Privacy (PGP) or encrypted password, the authentication scheme and information associated with it should be listed in items 0b and 0c. These items contain the authorization information for the sender of an update request and help determine if the request is coming from a valid sender. These items are REQUIRED when a Host is being deleted. Item 0b is the type of authentication scheme. It can have values MAIL-FROM, CRYPT-PW, or PGP. Item 0c is the authorization information for the selected authentication scheme. As shown by the table below, items 0b and 0c are REQUIRED only when CRYPT-PW is the selected authentication scheme. The different items 0b and 0c combinations are: If Item 0b is Then Item 0c is MAIL-FROM Ignored. The FROM field in the mail header of an update message will be checked to verify the sender. MAIL-FROM is the DEFAULT authentication scheme. CRYPT-PW Cleartext password (the plain text of the encrypted password). PGP Ignored. The sender should sign the entire update message with its secret PGP key and send it in cleartext to the InterNIC. Section 1 - Host Enter the handle, name and IP address of the Host to be deleted in items 1a, 1b, and 1c respectively. These items are REQUIRED for DELETE. Section 2 - Contact Leave this section blank.