After making DNS changes, you need to know when those changes are visible globally. Our free DNS propagation checker queries DNS servers across multiple continents and displays results side by side, so you can see exactly which regions have picked up your updates and which are still serving cached data.
What Is DNS Propagation?
DNS propagation is the process by which updated DNS records spread across the global network of recursive resolvers. When you modify a record at your authoritative nameserver, the change is immediately available there, but recursive resolvers around the world may continue serving the old record until their cached copy expires.
This is not a push mechanism. There is no broadcast signal that forces every DNS server on the internet to update simultaneously. Instead, each resolver independently decides when to re-query the authoritative server based on the TTL (Time to Live) value attached to the previously cached record.
Why Propagation Takes Time
TTL and Caching
Every DNS record includes a TTL value specified in seconds. When a resolver caches a record, it serves that cached version until the TTL expires. A TTL of 3600 means the resolver may serve stale data for up to one hour after a change. A TTL of 86400 (24 hours) means propagation could take a full day in the worst case.
This behavior is defined in RFC 1035 and is fundamental to how DNS scales. Without caching, every DNS query would hit the authoritative server directly, creating unsustainable load.
Resolver Behavior Varies
Not all resolvers respect TTL identically. Some large public resolvers like Google (8.8.8.8) and Cloudflare (1.1.1.1) are generally compliant, but ISP-operated resolvers may apply minimum TTL floors or cache records longer than specified. This means propagation timing is never perfectly predictable.
Negative Caching
If a resolver queried your domain before you created a new record and received an NXDOMAIN (non-existent domain) response, it caches that negative result according to the SOA minimum TTL. This can delay visibility of newly created records even if the positive TTL is low.
How to Use the Propagation Checker
Enter your domain name and select the record type you want to check (A, AAAA, MX, TXT, CNAME, NS, or SOA). The tool queries DNS servers in North America, Europe, Asia, South America, and Oceania, then displays the response from each location with timestamps.
Compare the returned values across all locations. If every server returns the new record, propagation is complete. If some still show the old value, those resolvers are serving cached data and will update once the TTL expires.
Practical Strategies for Faster Propagation
Lower TTL before changes. If you know a DNS change is coming, reduce the TTL on the affected record 24-48 hours in advance. Set it to 300 seconds (5 minutes) or lower. After the change has propagated, raise the TTL back to its normal value to reduce query load on your authoritative servers.
Verify at the authoritative server first. Before checking global propagation, confirm the change is live on your authoritative nameserver. If the authoritative server is still returning the old value, propagation cannot begin. Use the DNS lookup tool to query your authoritative nameservers directly.
Check MX records after migrations. Email server migrations are particularly sensitive to propagation delays. During the transition, both old and new mail servers should accept mail for the domain. Monitor MX propagation closely using this tool and cross-reference with the MX Lookup tool to verify the new configuration.
Validate SPF after IP changes. If your sending IP changes, update your SPF record and monitor its propagation. Messages sent from the new IP before the updated SPF record has propagated globally will fail SPF checks, potentially triggering spam filters or DMARC failures.
Common Propagation Issues
Inconsistent results after 48 hours. If some resolvers still show old data well beyond the original TTL, the issue may be a resolver that applies non-standard minimum TTLs, or a stale zone transfer to a secondary nameserver. Verify all authoritative servers return consistent data.
Records appear then disappear. This can indicate a split-brain condition between authoritative nameservers serving different versions of the zone. Check NS records and SOA serial numbers for consistency.
Regular propagation monitoring after every DNS change protects your email deliverability and ensures your infrastructure is globally consistent.
FAQ
What is DNS propagation?
DNS propagation is the process by which updated DNS records spread across the global network of recursive resolvers after a change is made at the authoritative nameserver. Because DNS relies on caching, resolvers around the world continue serving the old record until their cached copy expires based on the TTL (Time to Live) value. Propagation is complete when all resolvers worldwide are returning the new record.
How long does DNS propagation take?
DNS propagation typically takes anywhere from a few minutes to 48 hours, depending primarily on the TTL value set on the previous version of the record. A record with a TTL of 300 seconds (5 minutes) will propagate much faster than one with a TTL of 86400 seconds (24 hours). Some ISP resolvers may apply minimum TTL floors that extend propagation beyond the expected timeframe.
Why aren't my DNS changes showing up?
The most common reason is that recursive resolvers are still serving the cached version of your old record and the TTL has not yet expired. Other causes include making changes at the wrong DNS provider, zone transfer failures between primary and secondary nameservers, or negative caching of a previous NXDOMAIN response. Verify your changes are live on your authoritative nameserver first using the DNS Lookup tool, then monitor global propagation with our Propagation Checker.
How can I check if DNS has propagated?
Use our DNS Propagation Checker to query DNS servers across multiple continents simultaneously. Enter your domain and select the record type you changed. The tool displays the response from each global location so you can see which regions have picked up the update and which are still serving cached data.
Can I speed up DNS propagation?
You cannot force remote resolvers to clear their cache, but you can prepare for faster propagation by lowering the TTL on the affected record 24-48 hours before making changes. Set it to 300 seconds or lower so that when you make the actual change, resolvers worldwide will re-query within minutes. After the change has fully propagated, raise the TTL back to a normal value to reduce query load on your authoritative servers.
Stay on top of your email infrastructure. Sign up for the InboxTooling newsletter for deliverability tips, tool updates, and best practices.