← Resources

How to Check DNS Propagation After Changing a Record

Ekim 4, 2026 · IpDnsHub · 2 views ·
dns propagation

What “Propagation” Really Means

DNS changes are not pushed out to the internet. When you edit a record, it changes immediately on your authoritative nameservers. Every other resolver keeps using its cached copy until the cached entry expires, as set by the record’s TTL (Time To Live). “Propagation” is simply the time it takes for those caches to expire and fetch the new answer. Our guide Understanding DNS propagation explains the background in detail.

So checking propagation means answering three questions in order: is the change correct at the source, which resolvers already see it, and is your own device still holding an old copy?

Step 1: Check the Authoritative Nameservers

First make sure the change is actually live where it matters. Find the nameservers of your domain with our DNS Record Lookup (NS record), then ask one of them directly:

dig @ns1.your-dns-provider.com example.com A +short
nslookup example.com ns1.your-dns-provider.com

If the authoritative server still returns the old value, waiting will not help. The most common reason is that the record was edited at a provider that is not authoritative for the domain — for example in the hosting panel while the domain’s nameservers point to Cloudflare.

Step 2: Compare Public Resolvers

Next, see what large public resolvers return. Our DNS Propagation Checker queries several resolvers in different networks at once and shows each answer side by side. Typical results:

  • All resolvers show the new value: the change is effectively complete.
  • Mixed results: normal during propagation. Resolvers that queried the record shortly before your change keep the old answer until its TTL runs out.
  • Different addresses that are all correct: if your site uses a CDN, resolvers in different places may receive different addresses. That is not a propagation problem.

You can also check the remaining cache time: the TTL shown by a resolver counts down. When it reaches zero, that resolver will fetch the new record on the next query.

Step 3: Clear Your Own Caches

If public resolvers already show the new value but your browser still opens the old site, the old answer is cached on your side:

  • Windows: ipconfig /flushdns
  • macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  • Chrome: open chrome://net-internals/#dns and clear the host cache.
  • Router: many home routers cache DNS too; restarting the router clears it.

Google Public DNS and Cloudflare’s 1.1.1.1 also offer public pages where you can ask them to drop their cached copy of a name, which helps when your users rely on those resolvers.

How to Make Future Changes Faster

  1. A day or two before a planned change, lower the record’s TTL, for example to 300 seconds.
  2. Wait at least as long as the old TTL, so all caches pick up the short TTL.
  3. Make the change. Caches now expire within minutes.
  4. After everything works, raise the TTL again to reduce query load.

Nameserver changes are slower than record changes, because the delegation records in top-level domains such as .com are cached for up to two days. Plan nameserver moves with that in mind.

Quick Checklist

  • Authoritative nameservers return the new value.
  • Propagation Checker shows the new value on most resolvers.
  • Local caches cleared.
  • Site loads and responds — confirm with Is My Site Down.

Still stuck? Read why DNS changes are not showing for less obvious causes.