Why does updating a domain's nameservers take so long?

BronzeByte picture BronzeByte · Nov 26, 2011 · Viewed 48.9k times · Source

When I change my domain's (a dot com) nameservers it can take up to 2 days.
I know that that's usual, but WHY is that?

Just curious because my webhosting went down and I have to wait now because I changed nameservers, why?

EDIT:
Did some little research and my webhosting says it can MAXIMUM take up to 24 hours.
Ok, I knew it was around 24 - 48 hours, but it is apperently only 24 hours.
Anyways, I found this article: http://www.tech-faq.com/how-to-flush-dns.html
And it says that you can flush DNS with ipconfig blabla, also already knew that.
But what is remarkable is that this is standing at the second paragraph:

The MaxCacheTtl represents the maximum time that a DNS lookup%u2019s results will be cached for. The default value is 86,400 seconds. If this value is set to 1, DNS entries will only be cached for a single second.

Now take your calculator and type in: 86,400 / 60 / 60 = TADAH!! 24 (hours)
I haven't tried it yet because the registery key wasn't present in my registery :S

Answer

Alnitak picture Alnitak · Nov 26, 2011

When you change your nameservers you have to ensure that the old nameservers also contain the new information, otherwise some resolvers won't notice that the delegation in the .com zone has changed.

For more information see https://serverfault.com/questions/322490/what-is-the-correct-behaviour-when-nameservers-change/322524#322524