Skip to content
ENID
DNS

How to Check DNS Propagation: A Practical Guide

Understand what DNS propagation is, how to check it properly, and what to do when changes don't appear everywhere.

Published 3 min read

1. What is DNS propagation?

DNS propagation is the time it takes for a change to a DNS record to become visible across the internet. Nothing is actually pushed out. When you change a record at your DNS provider, the new answer is available immediately on your authoritative nameservers. Everyone else keeps seeing the old answer until the copy cached by their resolver expires.

Propagation time is bounded by the TTL (time to live) of the old record, plus caches outside your control. A 300 second TTL usually means minutes; a 86400 second TTL can mean a day.

2. How it works

  1. Change record
  2. Nameserver update
  3. Resolver cache
  4. Propagation complete
  1. You edit a record at your DNS provider. The authoritative nameservers answer with the new value straight away.
  2. Recursive resolvers (your ISP, Google, Cloudflare, your office) that asked for the record earlier still hold the old answer.
  3. Each resolver discards its copy when the TTL runs out and asks the authoritative nameservers again.
  4. Once every cache has expired, the whole internet sees the new value.

Changing the nameservers of a domain at the registrar is slower, because the delegation is stored at the registry and often has a TTL of up to 48 hours.

3. How to check DNS propagation

Use more than one method, because a single resolver tells you very little.

  1. Online lookup. Enter the domain in the DNS Propagation Checker and compare the answers from several public resolvers. If they all match, the change has reached the major resolvers.
  2. Command line. Ask a specific resolver directly:
dig example.com A @8.8.8.8
dig example.com A @1.1.1.1
nslookup example.com 1.1.1.1
  1. Ask the authoritative server. dig example.com A @ns1.yourprovider.com shows what your DNS provider serves. If it is already correct there, the problem is caching, not the record.
  2. Check your device last. Browsers, operating systems, and routers cache DNS as well.

4. Common issues

  • Different answers from different resolvers. Normal while caches expire. Wait for the old TTL, then check again.
  • Still seeing the old site. Flush the local cache (ipconfig /flushdns on Windows, resolvectl flush-caches on many Linux systems) and restart the browser.
  • SERVFAIL after a nameserver change. Often an old DS record (DNSSEC) at the registrar. Remove or update it.
  • Change made in the wrong place. DNS records live at the provider whose nameservers your domain actually uses. Check the NS records first.
  • Proxy services. If a CDN proxy is on, lookups return the CDN address, not your server.

5. Best practices

  • Lower the TTL (for example to 300 seconds) at least one old-TTL period before a planned change, then raise it again afterwards.
  • Keep the old server running until the TTL has fully expired.
  • Change one thing at a time so a problem is easy to trace.
  • Write down the previous values so you can roll back.

6. FAQ

How long does DNS propagation take?

From a few minutes to 48 hours, depending on the old TTL and where the change was made. Record edits are usually faster than nameserver changes.

Can I speed it up?

You cannot force other resolvers to refresh. You can only lower the TTL before the change and flush your own caches.

Is a propagation checker accurate?

It shows what the resolvers it queries answer at that moment. It cannot see every resolver, so treat it as a strong hint, not a guarantee.

Related guides

Enter to open, Esc to close

Scroll to Top