What Is DNS Propagation?
DNS propagation is the time it takes for DNS changes — like updating nameservers or changing an A record — to be reflected across all DNS servers worldwide. When you make a DNS change, it doesn't happen instantly. Instead, the update must ripple through a vast network of recursive resolvers, each with their own cached copy of your records.
This process typically takes anywhere from a few minutes to 48 hours, depending on several factors.
How DNS Resolution Works
To understand propagation, you need to understand DNS resolution:
- User's browser asks the local DNS resolver (usually your ISP) for the IP address of
example.com. - Local resolver checks its cache. If found and not expired, it returns the cached result immediately.
- If not cached, the resolver queries the root nameservers, which direct it to the .com TLD servers.
- The TLD servers point to your domain's authoritative nameservers.
- The authoritative nameserver returns the actual DNS record (e.g., A record with your IP).
- The local resolver caches the result for the duration specified by the record's TTL.
The Role of TTL (Time to Live)
TTL is the single most important factor in DNS propagation speed. Every DNS record has a TTL value expressed in seconds that tells resolvers how long to cache the record.
| TTL Value | Duration | Use Case |
|---|---|---|
| 300 | 5 minutes | Frequently changing records, failover |
| 3600 | 1 hour | Standard records |
| 86400 | 24 hours | Stable records that rarely change |
Pro tip: If you're planning a DNS migration, lower your TTL to 300 seconds (5 minutes) at least 24–48 hours before making the actual change. This ensures caches worldwide expire quickly once you switch.
Why Propagation Isn't Instant
Even with a low TTL, several factors can slow propagation:
- ISP caching: Some ISPs ignore TTL values and cache records longer than specified to reduce load.
- Resolver behavior: Large public resolvers like Google DNS (8.8.8.8) and Cloudflare (1.1.1.1) generally respect TTLs, but smaller ISP resolvers may not.
- Negative caching: If a resolver previously received an NXDOMAIN (domain not found) response, it may cache that negative result.
- Operating system cache: Your local machine caches DNS lookups independently of the resolver.
How to Check Propagation Status
Use Waqaya's DNS Health Check tool to test your domain's DNS records across 18+ global resolvers. The tool shows you exactly which resolvers have picked up your new records and which are still serving cached data.
Manual Checks
You can also check specific resolvers from the command line:
# Check Google's resolver
dig @8.8.8.8 example.com A
# Check Cloudflare's resolver
dig @1.1.1.1 example.com A
# Check your current resolver
dig example.com ACommon DNS Change Scenarios
Changing Web Hosting
When switching hosting providers, you typically update your A record or CNAME. Lower TTL beforehand, make the change, and monitor propagation. Keep the old server running until propagation completes.
Migrating Email (MX Records)
Email migration is more sensitive. Lower MX record TTL in advance, switch the records, and monitor. Some email may still arrive at the old server during propagation — ensure both servers are active.
Enabling a CDN
CDN setup usually involves changing your A record to a CNAME pointing to the CDN provider. This is a standard propagation scenario — expect 15 minutes to 24 hours depending on TTL settings.
Key Takeaways
- Always lower TTL before changes — plan 24–48 hours ahead
- Use multiple resolvers to verify propagation (try our DNS checker)
- Keep old infrastructure running until propagation completes
- Be patient — full global propagation can take up to 48 hours in rare cases