How long does DNS propagation usually take?

It depends on the previous TTL, resolver behavior, and the record type, but it can range from minutes to 48 hours. Lowering TTL before the change is the best way to shorten that window.

What does it mean if some resolvers changed and others did not?

It usually means propagation is still in progress or certain ISP or enterprise resolvers are holding cache longer than others. The zone itself may already be correct.

How do I tell DNS propagation apart from browser or CDN cache?

Compare resolver responses with Propagation Check, then compare actual content and redirect behavior with HTTP Check. If DNS is consistent but content differs, the cache layer is likely elsewhere.

Why DNS Changes Take Time to Propagate

A practical guide to separating TTL effects, resolver caching, and CDN/browser caching when DNS changes appear inconsistent across regions or networks.

Diagnose your site now

Problem

You changed a DNS record, but different networks or regions still return different answers. Before waiting blindly, you need to determine whether this is normal propagation or an actual configuration problem.

Symptoms

Different resolvers return different IPs or different record states.
The site points to the new server in one region but the old server in another.
NXDOMAIN or stale values still appear intermittently after a record change.
HTTP behavior looks fine while DNS results remain inconsistent.

Top 3 Causes

Previous TTL is still active - A high TTL keeps old answers alive until cache expiry.
Resolver-specific caching - ISP, enterprise, and public resolvers do not age records identically.
Non-DNS cache confusion - DNS may already be correct while CDN or browser caches still show the previous content.

Diagnose with DechoNet

Propagation Check to compare responses across public resolvers.
DNS Lookup to verify the current intended record values and TTL.
HTTP Check to see whether stale behavior comes from content caching rather than DNS.

Resolution Checklist

Confirm what TTL was in place before the change and use that value to set expectations.
Record which resolvers still return stale answers in Propagation Check.
Verify with DNS Lookup that the current record and TTL match the expected configuration.
If HTTP still serves old content, review CDN or proxy cache invalidation instead of blaming DNS alone.
Clear local cache only as a local test, not as proof that global propagation is complete.

When to Escalate

Escalate to the DNS provider if the authoritative answer is wrong or never updates.
Escalate to the registrar if a nameserver delegation change is still not reflected after the expected window.
Escalate to the provider if most public resolvers still serve stale data and zone publication may have failed.