2

I'm working with a website that changed servers, and even after it fully switching over, I still get the old IP when doing nslookup.

I've tried flushing my DNS on my router and computer, and it still fails to return the correct IP.

Via DD-WRT Shell: killall -1 dnsmasq Via Mac (10.6) shell:

4
  • Do you have a local host file that might be returning the incorrect IP? Can you try running nslookup and specifying an external server like OpenDNS to see what the IP resolves to? What OS are you running?
    – user114321
    Commented Jan 19, 2012 at 6:42
  • I ran an online NSlookup from MyDNSTools and it shows the new IP.
    – Joseph
    Commented Jan 19, 2012 at 6:48
  • 1
    Global propagation of DNS changes can take up to 24 hours. Try a different DNS server (like Google's): nslookup example.com 8.8.8.8 Commented Jan 19, 2012 at 7:14
  • 2
    DNS does not propagate. It's a cached system. The questioner apparently knows this, as xe is trying to flush caches. Xe probably hasn't flushed all of the caches that are involved. Moreover: The 24 hours figure is untrue. Caching depends from TTLs, which many caching servers will allow to be anything from 1 second to 1 week.
    – JdeBP
    Commented Jan 19, 2012 at 11:23

1 Answer 1

0

DNS changes must be renewed by other DNS servers, it usually takes some time, depending upon the caching of the DNS server you use.

Take a look at this site to find if your domain has been cached to all the DNS servers.

whatsmydns.net

2
  • DNS does not propagate. Changes are never "sent to all the DNS servers", especially because the majority of those servers are not interested in your domain. DNS information is requested and cached. Commented Jan 20, 2012 at 14:14
  • @grawity ok did not know that.
    – HackToHell
    Commented Jan 20, 2012 at 14:17

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .