DNS Propagation Checker
Check if your DNS changes have propagated across the globe. Query multiple DNS resolvers simultaneously and compare results.
What this tool checks
This DNS propagation checker queries multiple global DNS resolvers simultaneously and compares their responses. It supports all common record types:
How DNS propagation works
When you change a DNS record at your registrar or DNS provider, the update first applies to your authoritative nameservers. Other DNS resolvers around the world (like Google, Cloudflare, and your ISP) cache DNS records for a duration set by the TTL (Time To Live). Until their cached copy expires, they continue serving the old record. This is why changes appear to propagate gradually - different resolvers refresh at different times depending on when they last cached the record.
Tips for faster DNS propagation
- Lower the TTL first. At least 24-48 hours before making changes, reduce the TTL to 300 seconds (5 minutes).
- Wait for the old TTL to expire. If your TTL was 86400 (24h), wait 24 hours after lowering it before making changes.
- Verify with this tool. Check propagation from multiple resolvers. Once all return the new value, raise the TTL back up.
- Flush local caches. Run
sudo dscacheutil -flushcache(macOS) oripconfig /flushdns(Windows) for immediate local testing.
Frequently asked questions
What is DNS propagation?
How long does DNS propagation take?
Why do different DNS servers show different results?
What do the different record types mean?
How can I speed up DNS propagation?
Is this tool free?
How does DNS propagation work?
When you update a DNS record, the change does not broadcast to all resolvers at once. Instead, each resolver caches the old value for its remaining TTL, then fetches the new record on its next lookup. The process involves four types of servers:
- 1. Recursive resolver - your ISP's or public DNS server (8.8.8.8, 1.1.1.1). Receives queries from your device and caches responses.
- 2. Root name server - 13 root server clusters worldwide. Directs resolvers to the right TLD name server (e.g., .com, .io).
- 3. TLD name server - operated by the registry (Verisign for .com). Points to your domain's authoritative name server.
- 4. Authoritative name server - your DNS host (Cloudflare, Route 53, etc.). Returns the actual record value.
When you change a record, the authoritative server updates immediately. Resolvers worldwide then serve the old cached value until their TTL expires and they re-query. "Propagation" is just the gradual expiry of caches across thousands of resolvers.
DNS record types explained
| Record | Purpose | Common use |
|---|---|---|
| A | Maps hostname to IPv4 address | Main website, API endpoints |
| AAAA | Maps hostname to IPv6 address | IPv6-enabled services |
| CNAME | Alias to another hostname | www → apex, CDN endpoints |
| MX | Mail server routing with priority | Email delivery (Gmail, Outlook) |
| TXT | Arbitrary text data | SPF, DKIM, domain verification |
| NS | Authoritative name servers for the zone | Delegating DNS to a provider |
| SOA | Zone authority metadata | Serial number, refresh intervals |
| CAA | Restricts which CAs can issue certificates | Prevent unauthorized SSL issuance |
| PTR | Reverse DNS - IP to hostname | Email server reputation (rDNS) |
How long does DNS propagation take?
Most DNS changes reach the majority of global resolvers within 15 minutes to a few hours. Full worldwide propagation - including resolvers in regions with longer cache lifetimes - can take up to 48 hours, but this is rare for modern DNS providers.
The primary variable is your record's TTL (Time to Live). A TTL of 86400 (24 hours) means resolvers can cache the old value for up to 24 hours before re-querying. A TTL of 300 (5 minutes) means changes reach most resolvers within minutes.
Propagation speed by TTL
TTL 86400 → up to 24 hours · TTL 3600 → up to 1 hour · TTL 300 → up to 5 minutes · TTL 60 → near-instant
How to speed up DNS propagation
- Lower your TTL before the change. 24–48 hours before you plan to update a record, reduce its TTL to 300 seconds. Once all existing caches expire, your change will propagate in minutes. After the cutover, raise the TTL back to 3600 or 86400.
- Wait for the old TTL to expire first. Lowering the TTL does not speed up propagation immediately - resolvers that already cached the record will hold it for the original TTL. Check this tool to confirm the old value is gone before making the change.
- Flush your local DNS cache. Your machine caches DNS independently of resolvers. On macOS:
sudo dscacheutil -flushcache. On Windows:ipconfig /flushdns. On Linux:sudo systemd-resolve --flush-caches. - Test with multiple resolvers. Use this tool to check Google (8.8.8.8), Cloudflare (1.1.1.1), and regional resolvers simultaneously. If some show the new record and others do not, propagation is still in progress.
Why is my DNS not propagating?
Old TTL has not expired yet
The most common cause. Check the TTL of the original record. If it was 86400, resolvers that cached it recently will not re-query for up to 24 hours.
You edited the wrong zone
Verify the change exists in your authoritative name server by querying it directly: dig @ns1.yourprovider.com yourdomain.com A. If the new record is not there, the change was not saved.
CNAME conflict
You cannot have a CNAME on the same name as any other record type (including another CNAME). A conflicting record silently wins, and the CNAME never resolves as expected.
NS records not delegated correctly
If you recently moved to a new DNS provider, check that your domain registrar updated the NS records to point to the new provider. Without correct NS delegation, changes to the new provider have no effect.
Reliable public DNS servers
| Provider | IPv4 | Notes |
|---|---|---|
| Cloudflare | 1.1.1.1 / 1.0.0.1 | Fastest average response globally; privacy-focused |
| 8.8.8.8 / 8.8.4.4 | Most widely used; reliable global coverage | |
| Quad9 | 9.9.9.9 / 149.112.112.112 | Blocks malicious domains; Swiss-based, privacy-first |
| OpenDNS | 208.67.222.222 / 208.67.220.220 | Content filtering options; Cisco-operated |