0

After migrating from different dedicated servers from completely different providers, I then had to update nameservers on hundreds of domains from different registrars.

I notice that GoDaddy DNS updates typically occur flawlessly within 2 hours. Netfirms, so far is jumping back and forth between the old nameservers and the new... but it's still within the 24-48 hour window - I am hoping it will stabilize.

I am wondering if such a discrepancy among domain registrars is normal, or if there might be something I've misconfigured?

inac
  • 509
  • 2
  • 9
  • 20
  • At first I thought this might be a technical problem in general, but my hunch is that it is discrepancy among registrars - here is the thread on the technical problem in general: http://serverfault.com/questions/155355/nameserver-change-jumps-back-to-old-nameservers-cause – inac Jun 28 '10 at 07:21

1 Answers1

1

It will all depend on the methods used by the individual registrars.

The definitive source should be the 'whois' service, so always check that first. This will list the names of the nameservers currently listed for your domain.

After that, check that the TLD's name servers have been updated by the registrar. On Unix:

% dig @<tld-server> <domain> NS

Where <tld-server> for .com might be a.gtld-servers.net, and for a .uk domain would be ns1.nic.uk, etc.

If you don't know what your TLDs name servers are, use this:

% dig @a.root-servers.net. <tld> NS

At this point, you should have been able to confirm that the higher levels of the DNS hierarchy have the right information - namely the current name servers for your domain.

For each such name server, then run:

% dig @<nameserver> <domain> SOA
% dig @<nameserver> <domain> NS

The first command will return the SOA record. In general each of them should have the same serial number present. If they don't, then their servers are not yet synchronised.

The second command returns the authoritative version of the NS records as maintained by your domain registrar. In general these should match whatever's in the TLD's DNS servers.

Alnitak
  • 20,901
  • 3
  • 48
  • 81
  • By serial number, do you mean the number following: Got answer: ->>HEADER<<- opcode: QUERY, status: NOERROR, id: – inac Jun 28 '10 at 21:44
  • no - it's the third field in the SOA record - usually in yyyymmddnn format, or UNIX time. – Alnitak Jun 28 '10 at 23:29
  • hmm, looks like you need more parameters for serial to show... dig +nocmd ogi.edu any +multiline +noall +answer http://www.madboa.com/geek/dig/ – inac Jun 29 '10 at 08:59
  • "Upgraded" to new problem @ http://serverfault.com/questions/155847/dig-vs-whois-on-nameserver-update-and-reference-to-unknown-fqdn – inac Jun 29 '10 at 09:12