What is DNS Propagation & How to Flush DNS Cache
A deep dive into recursive caching resolvers, authoritative nameservers, Time-to-Live (TTL) mechanics, and practical cache-clearing commands across every major operating system.
When you update an A record, change your mail exchange (MX) server, or point your domain to a new web host, the update does not take effect universally across the planet in a single millisecond. Instead, you experience a delay known as DNS Propagation.
To understand why this delay exists and how to bypass local caching bottlenecks during migration, we must explore the hierarchical resolution tree of the Domain Name System.
01 The 4 Layers of DNS Resolution
Every time a visitor enters yourdomain.com in a browser, a 4-step lookup chain executes:
Your local operating system (Windows, macOS, iOS, Android) first checks its own local RAM cache and your hosts file to see if the domain IP was queried recently.
If not found locally, the request queries your ISP's resolver or public resolvers like Cloudflare (1.1.1.1) or Google (8.8.8.8). If the resolver has the record cached, it replies immediately with a non-authoritative answer.
If the recursive resolver has no cache, it contacts the 13 global root server clusters, which redirect the query to the Top-Level Domain (TLD) nameservers (e.g., the .com registry managed by Verisign).
The TLD server points to your domain's specific authoritative nameservers (e.g., Cloudflare, Route 53, or your registrar). The authoritative server returns the final IP address along with a TTL (Time to Live) value.
02 The Mathematics of TTL (Time to Live)
The TTL (Time to Live) is a 32-bit signed integer value expressed in seconds that tells recursive resolvers how long they are permitted to store and serve a copy of the DNS record without querying the authoritative nameserver again.
Common TTL Values & What They Mean:
- 300 seconds (5 minutes): Ideal for active migrations. Changes propagate globally within 5 minutes of nameserver updates.
- 3600 seconds (1 hour): Standard recommended balance for production websites.
- 86400 seconds (24 hours): High-cache stability. Changes will take up to a full day to reflect worldwide.
Webmaster Tip for Migrations: 48 hours before migrating servers, reduce your domain's TTL from 86400 to 300. This guarantees that when you switch IP addresses on migration day, worldwide downtime is virtually zero!
03 How to Flush DNS Cache on Any Device
If your website has moved to a new server but your own computer still displays the old host, your local operating system or browser cache is holding stale records. Here are the exact commands to flush it:
Press Win + R, type cmd, press Enter, and run:
ipconfig /flushdns
Expected output: Successfully flushed the DNS Resolver Cache.
Open Terminal (Cmd + Space → Terminal) and run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
sudo resolvectl flush-caches
# Or on older systemd distributions:
sudo systemd-resolve --flush-caches
Chromium browsers maintain a separate internal socket pool. Paste this into your address bar and click Clear host cache:
chrome://net-internals/#dns
04 How to Test Global Propagation Accurately
Because your local machine may reflect cached responses, never rely solely on your own browser to confirm DNS changes.
Instead, use the CheckHostNow DNS Lookup Tool to query authoritative global nodes across North America, Europe, Asia, and South America simultaneously. You can query A, AAAA, CNAME, MX, TXT, and NS records to verify whether authoritative resolvers have fully synchronized.
Verify Your Domain Propagation Now
Check DNS records across Cloudflare DNS and Google Public DNS instantly.