NetDig›Learn›DNS
DNS6 min read

DNS Change Not Propagating After 48 Hours

If your DNS change still shows the old value 48 hours later, it's not just slow propagation — something is wrong. Here's how to find and fix it.

First: Confirm the Change Was Saved

Before troubleshooting propagation, verify the change actually exists on your authoritative nameserver. Query the nameserver directly:

dig @ns1.yourregistrar.com yourdomain.com A

Replace ns1.yourregistrar.com with one of your domain's actual nameservers (find them with an NS lookup). If the direct query shows the old value, the change wasn't saved — log back into your DNS provider and re-enter it.

Quick check: Run a DNS Lookup — it queries Google's DNS which refreshes frequently. If it shows the new value, the problem is local caching, not propagation.

Check Multiple Global Resolvers

Run the DNS Propagation Checker to query 20+ resolvers worldwide. This tells you:

  • Which regions have the new value
  • Which are still serving the old value
  • Whether it's a widespread issue or isolated to specific resolver networks

Common Causes of Stuck Propagation

  • Very high TTL — a TTL of 86400 (24h) means a resolver that cached 23 hours ago won't refresh for another hour. Check your record's TTL.
  • DNS provider cache — some DNS providers cache changes on their own edge nodes. Try forcing a zone reload in your provider's dashboard.
  • Wrong nameservers — your domain's nameservers at the registrar may still point to the old DNS provider. Check with an NS lookup — are they pointing where you expect?
  • Nameserver mismatch — if you recently changed DNS providers, the old provider's nameservers may still be serving stale data to resolvers that cached the old NS records
  • Local OS cache — flush your local DNS: sudo dscacheutil -flushcache (Mac) or ipconfig /flushdns (Windows)
  • Browser cache — Chrome caches DNS internally. Open chrome://net-internals/#dns and clear the host cache.

Nameserver Propagation Takes Longer

If you changed your domain's nameservers at your registrar, this is a different process than changing DNS records. Nameserver changes are propagated by the TLD registry (.com, .org, etc.) and can take 24–48 hours. The TTL on NS records is typically set by the registry and can't be lowered.

Still Stuck After All This?

Contact your DNS provider's support with a screenshot of the propagation checker results. Also check your provider's status page — outages and zone synchronization issues do happen.

With typical TTLs of 1–24 hours, full global propagation takes up to 48 hours. If it's been longer and you've verified the change is saved on your nameserver, something else is wrong.

Your local OS or browser DNS cache is probably serving the old value. Flush your OS DNS cache and clear Chrome's internal DNS cache at chrome://net-internals/#dns.

Yes, during propagation different resolvers refresh at different times. Use the propagation checker to see which regions are still caching the old record. This should resolve on its own as TTLs expire.