Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

So I just changed webservers and I went to change my nameservers for the affected domains. I duplicated all of the DNS records on the new server, so that the transition would be easier, and then changed the nameservers. However, the changes seem to be not propagating - I can see that they now point to the new nameserver, but the sites don't resolve.

I set these up in Plesk for Linux using their wizard - is there anything I should or should not be doing?



I ran a check and for some reason, my new nameserver points to my old nameserver, like so: [] 39ms


share|improve this question
If you duplicated all the records are the NS records pointing to the old nameservers or something? – Dan Jul 14 '09 at 10:28
up vote 3 down vote accepted
        primary name server =
        responsible mail addr =
        serial  = 2009071403
        refresh = 15182 (4 hours 13 mins 2 secs)
        retry   = 1800 (30 mins)
        expire  = 1814400 (21 days)
        default TTL = 14400 (4 hours)

refresh set for 4h 13m 2s, wait for propagation to finish. Patience is a virtue :)

share|improve this answer
:-) Fair enough. – benjy Jul 14 '09 at 16:53

Use dig ( dig @< authoritative nameserver > < host or domain > would be a start) to see the current settings of the authoritative nameservers for the domain. They may not have picked up on the changes yet (for nameservers associated with hosted domains the records you can edit are often not the ones on the public nameserver but are copied to there after validation by a process owned by the hosting company; it's different in some cases or if the nameservers are actually your machines, of course). Even if the primary nameservers for the domain have the new information, any other DNS server that has recently resolved the domain and received the old information will have cached this for the TTL time and will not resolve the domain again until that expires (this is the reason for reducing the TTL time well before making a DNS change if you have control of that record (older versions of BIND set the TTL in the SOA record; TTL can also be set on an individual resource record)).

You can use dig ( dig < host or domain > )to see the records being returned by the nameserver your client is using, that should indicate which version it is using and the remaining TTL.

(I'm referring to dig above assuming you are using a GNU/LINUX/BSD client but I think there is a version of the tool on other platforms, too)

(I also started writing this wrote before reading your edit -- is that how it was originally set up? -- If so it could still be a caching issue, the TTL times should give a good indication of this. Unfortunately I have not familiar with DNSStuff is or its outputs so can't help there)

share|improve this answer

It may take upto 48 hours for DNS caches to timeout. Have you wait for a day or two?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.