Home / server / Questions / 234822
Accepted
darkAsPitch
Asked: 2011-02-13 12:15:23 +0800 CST

DNS Propagation Investigation Techniques?

  • 772

So I changed the nameservers for my domain name veeter.com about 5 days ago now - and the domain is still not resolving over the net.

It does intermittently, but then cuts out again every few hours.

I run 10+ other domains through the same dedicated server (running CentOS/WHM) and they are all up - so it has nothing to do with that.

I have asked my dedicated server support staff what the problem might be, they told me to "log into WHM and click on 'Add a DNS Zone' under the 'DNS Functions' section on the left hand side of the screen. Once you have done this and dns fully propagates it should resolve any intermittent dns issues you may be experiencing."

BUT there is already a DNS zone in place for the domain on my server - so what should I do?

My server host has gotten back to me finally stating it is most likely a problem with my ISP's caching mechanism and I should contact them - but somehow I doubt it - never noticed this problem before (and I migrate a lot of nameservers).

domain-name-system nameserver

3 Answers

  1. It's pretty hard to troubleshoot this without the actual domain name (which I can understand your not wanting to give here). Without a domain name all I can advise you to do is:

    1. Check at the GTLD servers to see if they know the correct NS's for your domain
      (Try a few of them)

    2. If the GTLD servers know the correct nameservers, ask some public DNS servers and see if they do too.

    3. If public DNS servers have the correct NS records they should be able to resolve stuff in your domain -- if not (or if it is intermittent) investigate your authoritative DNS servers to see what they're doing.

    5 days should be more than sufficient for any DNS propagation -- 24 hours is usually plenty of time. My suspicion is you have nameservers specified incorrectly somewhere or your authoritative servers are broken in some way...

    • 2
  2. Best Answer

    mcmeel actually answered this for me - so feel free to edit yourself in as the author or whatnot...

    mcmeel pointed me to dnscog.com - which gave me a report for my domain, stating that it was indeed attached to the "old" nameservers I once used on my server.

    Basically what happened was... when I first used WHM I had setup some custom default nameservers. A few months later, I changed them - but now whenever I create a new account through WHM it binds the domain to the old nameservers :S

    (Anybody who can help me change the "default nameservers" used when setting up a new domain through WHM will get an upvote from me!)

    • 1

  3. Use dig @localhost ANY +trace veeter.com, or go to use kloth's dig service. It returns:

    dig: couldn't get address for 'one.hostril.com': failure

    veeter.com. 172800 IN NS one.hostril.com.

    veeter.com. 172800 IN NS two.hostril.com.

    ;; Received 104 bytes from 192.55.83.30#53(m.gtld-servers.net) in 133 ms

    Is that a typo?

    • 0