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

Several hours ago i changed nameserver and DNS info on one of my domains at my domainregistar. When i access the domain from my home computers and when my friends access the domain they get to the old ip-adress hosting the dead site(We all live in Sweden).

But when i access the website from my mobile phone or through or North American proxies the website is shown like it should.

Why is this?, does it take time for change to take effect for diffrent locations/countries? I find it very strange and would like to start using my site now.

Do you think it will change or could i've been doing something wrong?

share|improve this question

migrated from Jun 26 '11 at 2:24

This question came from our site for professional and enthusiast programmers.

up vote 0 down vote accepted

Every DNS RR has a time-to-live value, which is set by the maintainer of the authoritative zone. Other DNS servers will usually hold on to an RR until that time expires before retrieving a new one.

There is no way for a DNS server to keep track of every server and client everywhere that has ever asked for an RR and tell it that a new one is available. None. You have to wait for the TTL to expire.

share|improve this answer
And some dns servers and individual computers ignore the TTL and just hang on to the cache for however long they feel like. Especially anything made by Microsoft. – Paul Tomblin Jun 26 '11 at 0:03
That's wholly inaccurate M. Tomblin. Ironically, one of the best known softwares that ignores TTLs was made by Netscape Communications Corporation. It, as several others, was a WWW browser. No actual DNS server software ignores TTLs. – JdeBP Jun 27 '11 at 6:57
@JdeBP: all resolvers (client libraries) ignore TTLs and don't forward TTL information to their callers, and those callers are allowed to cache as long as they want. It's not the best of ideas, but there it is. And notwithstanding your wishes, most versions of Microsoft's DNS implementation need to be forced to flush expired RRs — I've been involved with support requests caused by this. – geekosaur Jun 27 '11 at 15:05
You don't understand what you're doing when you're telling people to run ipconfig /flushdns, then. These are not my wishes, kid. The simple truth is that you aren't flushing the server at all, and the Microsoft DNS server does not ignore TTLs. This whole "some DNS servers ignore TTLs" idea is just nonsense. No DNS server does this, and the idea that any of them do is an old wives' tale, that unfortunately you've bought into by not understanding where actually the DNS server is in what you are doing, M. geekosaur. – JdeBP Jun 28 '11 at 9:04
@JdeBP: so where exactly did that claim that I told people to run ipconfig come from? Do you actually know the distinction between server and client? – geekosaur Jun 28 '11 at 14:37

Give it ~24 hours. Different ISPs and DNS servers cache entries for different amounts of time.

(Also, this really belongs more on ServerFault than StackOverflow.)

share|improve this answer

Your Answer


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