At 8/21/01 11:24 AM, Steve Poirier wrote:

>WE have a customer who have a couple of domains with us. These domains, use
>dns host from a domain that is registered with networksolutions. He update
>DNS ip entries at network solutions.
>
>My question is: If he modified dns ip entries at networksolutions, does
>these ip addresses will be updated in the OpenSRS registry automatically and
>what is the delay.
>
>Example:
>-Main domain: domain.com  (at networksolutions
>-Domain 2: anotherdomaine.com (with tucows) uses ns1.domain.com
>-ns1.domain.com ip address has been updated in the nsi registry, will it be
>updated in the tucows registry.

You may be getting "registry" and "registrar" confused.

For a given TLD such as .com, there is only one registRY, in this case 
run by Verisign Global Registry services (formerly Network Solutions 
Registry).

When you use the domain's registRAR (such as Network Solutions registrar 
or OpenSRS) to update the DNS host addresses, it updates the Verisign 
registry, and all registrars (and the root servers) will see the new 
value. You do not need to update it with each registrar. Each registrar 
does not store their own value.

(I should point out that if you transfer a domain that has DNS hosts 
associated with it from NSI registrar to another registrar, then update 
the DNS host entries, NSI will still show the old IP addresses when you 
do a WHOIS on an NSI domain that uses the hosts. This is merely a 
cosmetic bug in NSI's WHOIS and other internal systems due to 
unbelievable incompetence or malice on their part, and does not affect 
the working of the domain or the root server entries, which have the 
updated values. There appears to be nothing you can do about this 
cosmetic problem, which confuses people. I suspect NSI leaves it this way 
because it scares people who have moved away: they can say "if you stayed 
with us, this wouldn't happen".)

It generally takes between 12-48 hours for all the root servers to be 
updated, just like any DNS change. And since there is a 2-day TTL cache 
on the root server records, you have to wait at least 2 days beyond that 
before you can even begin to assume that everyone is using only the new 
servers. (Note that this applies to .com, .net and .org; other root 
server implementations such as .cc and .tv appear to have shorter cached 
values and more frequent updates.)

--
Robert L Mathews, Tiger Technologies

Reply via email to