DNS Not Propagating?

Changed DNS but still seeing the old record? Check 14 public resolvers at once and learn whether it is stale cache, NXDOMAIN caching, or the wrong zone.

Find out whether it is really propagation

If a DNS change works in one place and fails in another, the problem is usually resolver cache. WhereIsDNS checks 14 public resolvers side by side so you can see whether the old answer is still cached, the new answer is live, or the record was never published where the world is looking.

Use the form above with the hostname and record type you changed. If most resolvers agree on the new value, the change is live and a few caches are lagging. If every resolver still shows the old value, re-check the authoritative DNS zone and nameservers.

What each pattern means

• Some old, some new: normal propagation. Wait for the record's TTL.
• All old: the change may not be published, or you may be editing the wrong DNS provider.
• NXDOMAIN mixed with answers: a negative cache is still remembering that the name did not exist.
• SERVFAIL on validating resolvers: suspect DNSSEC or broken delegation.

FAQ

How long should DNS propagation take?

Usually minutes to a few hours. The upper bound is the old record's TTL, and newly-created names can also be delayed by negative caching from the SOA minimum TTL.

Can I force DNS propagation?

You cannot force third-party resolvers to drop cached records. You can lower TTL before a planned change, flush local caches for your own machine, and wait for external caches to expire.

Why does it work for me but not someone else?

You and the other user are probably asking different recursive resolvers. One resolver may have fetched the new answer while the other still has the old answer cached.

What should I check first?

Check the changed record across resolvers, then check NS records to confirm the domain is delegated to the DNS provider you edited. If DNSSEC is enabled and you see SERVFAIL, compare DS and DNSKEY records.