What is the easiest way to check DNS propagation?

Use a web-based DNS propagation checker. Enter your domain, select record type (A, MX, CNAME, etc.), and it checks 50+ global servers instantly. Shows which servers have updated and which haven't.

How do I check DNS propagation from the command line?

Use nslookup (Windows) or dig (Mac/Linux). Example: 'dig example.com A' or 'nslookup example.com 8.8.8.8'. Each command queries one server — test against multiple servers like 8.8.8.8 (Google), 1.1.1.1 (Cloudflare), and 9.9.9.9 (Quad9) for a global view.

What does it mean when different servers show different results?

This is normal during propagation. Different DNS servers cache records independently and expire at different times. When you see different results from different servers, propagation is still in progress. When all servers show the same new record, propagation is complete.

Why does my local machine show the old DNS when the checker shows the new one?

Your local DNS cache hasn't expired. Flush it: Windows (ipconfig /flushdns), Mac (sudo dscacheutil -flushcache), Linux (sudo systemd-resolve --flush-caches). After flushing, your machine will query fresh DNS servers and see the updated record.

How To Check DNS Propagation

Get a detailed answer to how to check dns propagation along with step-by-step troubleshooting instructions and related DNS resources.

ReviewMyDNS is a free DNS propagation checker that queries 50+ global DNS servers to verify your DNS records. Check A, AAAA, MX, CNAME, TXT, NS, and SOA records instantly.

How to Check DNS Propagation

DNS propagation is the process by which a DNS change you make — adding an A record, updating an MX record, or modifying a CNAME — spreads from your authoritative nameserver to the thousands of recursive resolvers used by internet users worldwide. Because each resolver caches records independently for the duration of the record's TTL, different users may see different results for the same domain during propagation. Checking propagation means verifying which resolvers worldwide have picked up your new record and which are still serving the old one.

Method 1: Online Propagation Checker (Fastest)

An online DNS propagation checker queries multiple global DNS servers simultaneously and shows you the result from each one in a single view. Use the ReviewMyDNS propagation checker to check your domain across 50+ servers in North America, Europe, Asia-Pacific, South America, and Africa. Enter your domain, select the record type you changed (A, AAAA, CNAME, MX, TXT, NS), and click Check.

Interpreting the results: green rows with consistent values mean those servers have the new record. Rows showing the old value or no record are still caching the old data. A mix of old and new values is normal during propagation — it means the process is in progress. Once all servers show the new value, propagation is complete.

Method 2: Command-Line Tools

Command-line DNS tools let you query specific servers and see the raw DNS response:

# Query Google DNS for an A record
dig A example.com @8.8.8.8

# Query Cloudflare DNS
dig A example.com @1.1.1.1

# Query your ISP's default resolver
dig A example.com

# Check MX records globally
dig MX example.com @8.8.8.8
dig MX example.com @1.1.1.1

On Windows, use nslookup instead of dig:

nslookup example.com 8.8.8.8
nslookup -type=MX example.com 1.1.1.1

Which DNS Servers to Test Against

Testing against a representative set of resolvers gives you a reliable picture of global propagation status. The most important servers to check:

Google Public DNS: 8.8.8.8 and 8.8.4.4 — used by millions of devices worldwide
Cloudflare DNS: 1.1.1.1 and 1.0.0.1 — one of the fastest resolvers globally
Quad9: 9.9.9.9 — security-focused resolver with good global coverage
OpenDNS: 208.67.222.222 — widely deployed in corporate networks
Your ISP's default resolver: Reached by running dig without specifying a server

If all major public resolvers show the new record but some users still see the old one, their ISP resolver may cache beyond the record's TTL. ISP caching behaviour varies and is outside your control.

Understanding TTL and How It Affects Propagation Speed

The TTL (Time to Live) on a DNS record determines how long resolvers cache it. A TTL of 3600 means resolvers can serve their cached copy for up to one hour. To speed up future propagation, lower your TTL to 300 seconds at least 48 hours before making any planned DNS change. After the change, the low TTL ensures caches expire quickly, and most users see the new record within 5-15 minutes.

If your TTL was high (3600 or 86400) when you made the change, you cannot speed up propagation retroactively — you must wait for the TTL to expire on each resolver's cache. See Why DNS Is Not Updating After 24 Hours for a full troubleshooting checklist if propagation seems stuck.