Instantly check DNS propagation across 20+ global DNS servers. Verify that your DNS record changes have fully propagated worldwide — supports A, AAAA, CNAME, MX, NS, TXT, SOA, and more.
DNS propagation is the process by which updated DNS records spread across the internet's network of DNS servers worldwide. When you change a DNS record — such as pointing a domain to a new server's IP address — that change doesn't instantly appear everywhere. Instead, it gradually propagates from your authoritative nameserver outward to resolvers and caches globally.
This tool performs a live, real-time check against 20+ real DNS resolvers located across North America, Europe, and Asia-Pacific, so you can see exactly which regions have already received your updated record and which are still showing old data.
How Long Does DNS Propagation Take?
DNS propagation time depends primarily on the TTL (Time To Live) value set on your DNS record. TTL tells resolvers how long (in seconds) to cache a record before re-fetching it. Common propagation scenarios:
TTL = 300 (5 minutes) — Most resolvers update within 5–10 minutes. Ideal for migrations.
TTL = 3600 (1 hour) — Full propagation within 1–2 hours globally. The most common default.
TTL = 86400 (24 hours) — Can take up to 48 hours for all resolvers worldwide to update.
Registrar propagation — Changing nameservers at the domain registrar adds an extra 24–48 hours on top of TTL.
Pro tip: If you know you'll be making DNS changes, reduce your TTL to 300 seconds at least 24 hours before the change. Then raise it back after propagation is confirmed.
Why Check DNS Propagation?
Website migration — Confirm your new server's A record is live before decommissioning the old one.
Email deliverability — Verify MX records and TXT records (SPF, DKIM, DMARC) have propagated before sending campaigns.
CDN setup — Ensure CNAME records pointing to a CDN have reached all regions.
Nameserver changes — Confirm NS record updates after moving to a new DNS provider.
Troubleshooting — Diagnose why some users see an old site while others see the new one.
Frequently Asked Questions
Each DNS resolver independently caches records for the duration of their TTL. When you make a DNS change, resolvers only see the update after their cached copy expires and they re-query the authoritative nameserver. Resolvers in different regions or with different caching policies will update at different times — which is exactly what this tool shows you.
NXDOMAIN (Non-Existent Domain) means the DNS server returned a negative response — it has no record of that domain or record type. This could mean the record doesn't exist yet, the change hasn't propagated to that server, or the record genuinely doesn't exist. For a newly created record, NXDOMAIN at some servers is expected during propagation.
You can't force external resolvers to flush their caches, but you can minimise wait time by: (1) setting a low TTL (300s) 24+ hours before your planned change, (2) making the DNS change as quickly as possible once TTL is low, and (3) flushing your own local DNS cache with `ipconfig /flushdns` (Windows) or `sudo dscacheutil -flushcache` (macOS). After propagation, raise your TTL back to a higher value like 3600.
TTL (Time To Live) is a value in seconds that tells DNS resolvers how long to cache your record. A TTL of 3600 means resolvers keep the cached copy for 1 hour before re-fetching. Lower TTL = faster propagation but slightly higher DNS server load. Higher TTL = slower propagation but better performance and resilience to nameserver outages.
Even after DNS propagates, your browser, operating system, or ISP may still have a local cache of the old result. Try: flushing your local DNS cache, using an incognito/private browser window, trying a different network (mobile data vs. WiFi), or using an online proxy to check from a different location. The issue is almost always a local cache, not the DNS propagation itself.