How long does DNS propagation take?

What does this mean?

There is no universal countdown for a DNS change. The previous record’s TTL, negative caching, delegation caches and provider publishing behavior all matter. Some people can see the new value quickly while others retain an earlier cached answer. A quoted time range from a provider is guidance, not a promise for every resolver.

What should I check first?

Before a planned move, note the current TTL and ask your provider how far in advance to lower it. Keep the old service available during the overlap. Changing a TTL at the moment of migration cannot alter a copy that another resolver already cached under the previous longer TTL.

How can I diagnose the cause?

Check that the authoritative DNS provider shows the intended value for the exact hostname and record type. Use the DNS lookup to record one recursive resolver’s current answer and remaining TTL. Repeat at sensible intervals. A decreasing TTL is useful evidence but does not represent every visitor’s cache.

How do I fix it safely?

If answers never converge, inspect the active nameservers, stale AAAA records and DNSSEC rather than simply waiting indefinitely. Browser caching, CDN caching and application caching can also make a website look unchanged after DNS itself is correct. Separate those layers before flushing or changing settings.

Verify the fix and know when to contact your provider

Save old records before editing and maintain a rollback plan. Ask the provider for authoritative-query evidence when its zone display and public answers disagree. Include the time of the change, old TTL, name, type and returned values. Do not keep switching nameservers while diagnosing a single propagation problem.

Work through these checks in order

1. Record the old TTL before migration; it matters more for already cached answers than a TTL lowered after the move. Keep the old destination available during the planned overlap.
2. Check the authoritative provider’s saved value first, then note one recursive resolver’s answer and TTL at spaced intervals. These observations document progress without claiming a worldwide completion percentage.
3. If DNS matches but the old page appears, compare a private browser session and the provider’s documented cache controls. Avoid another DNS change until browser, application and CDN caching are separated.

Which tool can help?

DNS lookup · Nameserver checker

DNS tools show one resolver’s public answers. Record explainers do not authenticate a message, and calculators do not monitor a server. Use the evidence alongside your provider’s logs.