Read on if you are responsible for maintaining your domain name with Internic.

The coder.com web site is housed on a Debian Linux server connected to a dedicated T1 line. This T1 is connected to a network service provider who is connected to Sprintlink.

Our recent experience with attempting to switch DNS IP addresses in a timely fashion prompted me to write this short list of recommendations for dealing with Internic. Following it is commentary from readers.

The Government is in the process of revamping their role and Internic's role in regulating DNS and handing the role to a non-profit, so that Internic may cease to exist in the upcoming months. As long as the current system stands, this information should be relevent.

Recommendation #1: Always use the on-line forms located on the Internic web site: http://www.internic.net/help/templates.html.

Reasons:

1. Internic can change the rules, formatting, or requirements necessary for registering, modifying, and deleting a domain-name, contact, or host-name can change at any time.



• For example, the current Domain Template was revised to V. 4.0 in March 1998, and Internic no longer accepts forms earlier than V. 3.5 (June 1997). Internic will not warn you if you submit an outdated form.
• By the terms of their contract, you may be agreeing to changes that Internic makes in the future. In the case of Internic's Name Dispute Policy, by using their registration services you agree that you agree in advance to any changes made in the future. This is the only notice you will receive to this clause; you need to check their web-site for changes to the policy.



2. Many Web-providers supply their customers with revised Internic forms for them to submit. These forms should, in the least, be checked against the "official" versions on the Internic web site to guarantee that they are correct and the latest version.

Recommendation #2: Unless you are very experienced at submitting these forms via email, use the "Web step-by-step" form on the Internic web site, rather than the text form.

Reasons:

1. The forms themselves do not contain adequate instructions for filling themselves out. You will probably need to refer to supplemental instructions on the Internic site. The best and perhaps the only complete instructions are found on the Web step-by-step forms.
   • For example, the Host Template (ftp://rs.internic.net/templates/host-template.txt) refers to the "NIC Handle of a Host". There are also "Domain NIC Handles" and "Contact NIC Handles." These are distinct terms. The only place where it is defined how to find each Handle is in the web version of the template. It is not defined in the email forms or their instructions, nor in the glossary (http://www.internic.net/glossary) or the FAQ (http://www.internic.net/faq).

2. Use the "Web step-by-step" Domain Name form rather than the Web one-page Domain Name form, unless you are highly experienced with the process. In my experience the one-page form leaves out crucial information.
   • The step-by-step form links to definitions of terms as you encounter them. In my experience, these definitions are more accurate than those found elsewhere on the Internic site, i.e. the Glossary or the FAQ.
   • When making a modification, the one-page form suggests that you can chose a new Authentication Method on this form. ("Choose an Authentication Method: If you picked CRYPT-PW, please enter the password") This is incorrect; you must chose the same method that you previously registered. The step-by-step form (but not the web one-page form or the email form) explains, rather, that you have to use the Contact Template to change the Authentication Method.

Recommendation #3: The Internic web-site is inconsistant.

Recommendation #4: If you understand how, set your contacts to use encrypted passwords rather than the default authentication method. This is especially important if one contact is acting as Administrative, Technical, Zone, and Billing contact.

Reason:

1. If for some reason you cannot receive email at your registered email address, you will not be able to make any Internic changes, without a time-consuming fax-back process.
   • Internic cannot manually make any changes without the tracking number, which is (in theory) automatically sent to your email address. The system depends entirely on your ability to receive their email containing the tracking number.
   • If you change your email address or your email will be otherwise down, without changing your contact information with Internic, you will be unable to make changes. This is not the case if you are using CRYPT-PW or PGP.

The coder.com web-site was down for six days in May. This traumatic event could have been completely eliminated if I had known these four recommendations prior to making the necessary changes with Internic. These recommendations may help other website owners to avoid problems with Internic.

Your milage may vary; I am not an expert with networks and if you need an expert's advice you should consult with an expert.

Let me know if you find this document to be useful! -Daniel Allen

Commentary

For a proper move which requires changing of the primary DNS server, you transfer primary DNS rights to a server which won't be moving, a week or two in advance. Make sure this server has all the records. Then, on the day of the move, change the DNS records on the primary server to point to the new IPs. When your servers are setup at the new IPs, file a request with internic to change the primary server for your domains back to the original primary servers.

The key here is to have a server which is not moving do the primary DNS. You *cannot* hope for the Internic updates to coincide with the move. EVEN IF they process the change within 3 seconds, it can still take 3-7 days for peoples DNS servers to update the primary DNS address for the domain (whereas, a record for a DNS server updates in as little as a few hours, depending on the record info). Internic can't control how long it takes for other servres to update.

Preparation is the key.