At 6/22/02 8:59 AM, Charles Edmunds wrote on dev-list:

>Just wondering if there's any issues with opensrs.net updating their
>databases in the past 72 hours.
>
>I updated nameservers on mulitple domains to point to a new server and
>nothing has been propagated over yet.
>
>I've contacted support on my end and they say that the domains have been
>added to their list but have not managed to resolve to the new nameservers.

Well, three things to consider:

1. Are the updates shown when you log back into your management page and 
click "Nameservers"? If not, there might be something wrong at the 
reseller end (or you made a mistake in updating).

2. Assuming they are shown there, are they shown in OpenSRS's WHOIS? If 
so, OpenSRS knows about them.

3. Assuming they are in WHOIS, are they shown in the gtld-servers.net 
servers? Check that here:

  http://www.tigertech.net/cgi-bin/domaincheck.cgi

If none are listed there, there's something wrong at the Verisign/OpenSRS 
communications level, or at the Verisign registry level, assuming you 
really did change them three days ago. If they are listed there, your 
problem is either a) your local DNS is using a cached copy of the old 
data, in which case you'll just have to wait for your local DNS to pick 
up the changes, or b) the new nameservers you pointed the domain at 
aren't working (this isn't a propagation problem, of course, but you 
didn't define how you checked "nothing has been propagated" -- perhaps 
you're just finding the domain name doesn't resolve as expected).

Hope this helps. If you still have trouble, telling us the domain names 
and the desired nameservers would probably be useful; it's a little hard 
to tell you why your car won't start when you won't let us look at the 
car  :-)

By the way, this isn't really a dev-list question (that's for OpenSRS 
software development), so I changed the list to discuss-list.

------------------------------------
Robert L Mathews, Tiger Technologies

Reply via email to