Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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

I have a domain for which I updated the nameservers to point to my new server not long (~ 1 hour) ago:

The WHOIS report tells me it's been updated:

Why is that when I try to access the site or even ping it, it still resolves to the old server?

share|improve this question
Short answer: Flush your DNS cache. – John Gardeniers Aug 19 '10 at 1:42
See the bottom answer by @KarstLok. Your PC HOSTS file should be (temporarily) manually modified (after 12-48 hours, it will be automatically updated.). – tazo todua Jul 8 '15 at 13:33
up vote 7 down vote accepted

Unless you have set a nonstandard "time to live" on your old DNS server, you must wait a considerable amount of time (typically 1-7 days) for remote users' cached DNS records to expire. This ordinarily can be prevented by setting the TTL to something very short (e.g. 5 minutes); however, for obvious reasons, the TTL change should have been made at least a week in advance of the server change, and it cannot be done retroactively. At least you'll know what to do differently next time.


  1. If you are serving entirely static content, you should consider the option of simply keeping both servers up for a few days.

  2. If the server in question is a web server, you may be able to configure your old site to redirect visitors to the new site during the transition. Configure an entirely new "A" record as a subdomain (e.g. "") pointing to your new site's IP address. Then, on your old server, set up an HTTP refresh header (or the equivalent meta tag) redirecting all clients to the new site.

[edit] This answer is based upon the following assumptions:

  1. We presume that the probable cause is an A record that has been cached by various client machines, ISP nameservers, etc. We do not know the TTL for the stale A record associated with @NullUserException's domain. In my personal experience, web hosting companies seem to favor 48 hours as a default TTL, but others here have reported seeing other default values. We also find it highly unlikely that anyone has ever changed the default.

  2. We assume that @NullUserException wants everyone (not just himself) to be able to access the site at the new location; therefore, potential workarounds affecting only the local computer (e.g. flushing the local DNS cache or editing the local hosts file) are not offered.

  3. "DNS records" refers to DNS records in general, not any specific type of DNS record.

share|improve this answer
Finding the name servers and accessing a site at that domain are two different things. It appears the OP's problem is accessing a site at that domain. While the problem may in fact be with cached name server records as you've stated, it could just as well be with a cached A record or a misconfigured A or CNAME record. – joeqwerty Aug 18 '10 at 23:02
What I wrote above was based on what I would consider to be the most common problem with these first-time cut-over scenarios: a cached A record with a typical default TTL of 48 hours. Of course, you are absolutely welcome to suggest other potential causes. – Skyhawk Aug 18 '10 at 23:24
@Miles: I follow you. My answer and my comment to your answer was based on the fact that his access and ping were going to the old server, which suggests that he's trying to access his web site, which suggests an A or CNAME record problem. If it were an NS record problem then his tests wouldn't have resolved to anything, the old or the new server. Of course I meant no offense in my answer or comments. – joeqwerty Aug 19 '10 at 1:32
@joeqwerty: When I said "DNS records" above, I meant DNS records in general -- including A records, CNAME records, MX records, etc. I am a bit confused by your interpretation, because I never said anything specific about NS records (or any other particular type of DNS record) in my original answer. My logic: no matter which type of DNS record is being cached, it is likely subject to a 48-hour default TTL. – Skyhawk Aug 19 '10 at 2:32
@Miles: My apologies. In your answer you made mention of his DNS server and I took that to mean that you were referring specifically to his NS records and not A or CNAME records (or any other record for that matter). Sorry for any confusion I may have caused. – joeqwerty Aug 19 '10 at 2:51

When you say that when you try to access the site or ping it it's going to the old server, can you be more specific? Are you trying to go to If so, what is the A or CNAME record for www pointing to? Start at the top of the chain: run nslookup (or dig) and query for the name servers for the domain. Take those results and query those name servers for the A or CNAME record for the site. What do the results tell you?

share|improve this answer

Your problem will probably be solved within 48h, but in the meantime, if you need your pc to translate to another IP then the one your DNS comes up with, you can add the IP in your host file. In windows it's at c:/Windows/System32/Drivers/Etc/Hosts, you can edit it with notepad and add the following line:

Where is the IP you want to point to. Sometimes the only problem is your PC's DNS cache. Presuming your using Windows, you can type in a command prompt:

ipconfig /flushdns

This will flush the dns cache of your PC and maybe solves your problem, be sure to restart your browser after editing the host-file or flushing your DNS cache.

share|improve this answer
See my comment to joe's answer. Where did you come up with 48 hours? Did you just pick that number or are you merely propagating the DNS propagation myth? His NS records may have a TTL of 48 hours (which you would only know if you looked it up) but you have no idea what the TTL is for any other DNS records in his DNS zone. As it is, his question is likely an A or CNAME record problem. – joeqwerty Aug 19 '10 at 1:29
That's why I said "probably". His problem is not likely a A or CNAME problem, explain to me why DNS propagation is a myth, don't give me crap. – Karst Lok Aug 19 '10 at 7:20
I'm not giving you crap. How did you come up with 48 hours? Did you just pick a random number? Did you make an assumption that his DNS records had a TTL of 48 hours? DNS propagation is a myth because DNS records don't propagate. – joeqwerty Aug 19 '10 at 12:03

The problem is that your internet provider (or internal network's) cached DNS server has not yet been refreshed. You may wish to connect to a proxyserver (search for one on google). Once your external IP is different (as confirmed by checking on, do the following:

Clear your local DNS settings. On Windows, start a command prompt, and type:

ipconfig /flushdns

Re-load your page.

share|improve this answer

your DNS change can take up to 48 hours to filter down through all DNS resolvers. This is something that can not be avoided in almost all cases. unless you are very very close the the root. Just sit back and wait, if you can not get to in 24 hours you might want to contact the oporator of the nameservers.

share|improve this answer
We need to stop saying that "The DNS needs to filter down through all DNS resolvers" or "The DNS will take 48 hours to propagate" because that's not how DNS works. DNS records are cached not propagated. If the host has none of your DNS records in it's resolver cache then it will resolve the new information immediately. If it does have your DNS record in it's resolver cache then that information will persist for the remainder of the TTL. – joeqwerty Aug 19 '10 at 1:26

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.