What Is DNS Propagation? Why DNS Changes Take Time
DNS propagation is the process by which updated DNS records spread across DNS servers worldwide after a change is made. When you update your domain’s A record, change nameservers, or modify any other DNS record, the change isn’t instant. Cached copies of the old record exist on DNS resolvers around the world, and each one continues using the cached version until its TTL (Time to Live) expires. The time it takes for all these caches to refresh is what we call propagation.
Why DNS Changes Aren’t Instant
DNS is a massively distributed caching system. When a resolver looks up your domain, it caches the result for the duration specified by the TTL. If your TTL is 3600 seconds (1 hour), every resolver that cached your record will serve the old value for up to an hour before checking again.
The problem is that not all resolvers cached your record at the same time. A resolver in Tokyo might have cached it 5 minutes ago, while one in London cached it 55 minutes ago. When you make a change, Tokyo waits 55 more minutes while London queries again in 5 minutes.
Multiply this across the millions of DNS resolvers worldwide, each with different cache timings, and you get the propagation delay.
How to Minimize Propagation Time
Before the change:
- Lower your TTL to 300 seconds (5 minutes) at least 24 to 48 hours before the planned change
- Wait for the old high TTL to expire everywhere
- Now all resolvers are checking every 5 minutes
Make the change:
- Update your DNS records
- Within 5 minutes, most resolvers worldwide will see the new value
After the change:
- Verify propagation using DNS lookup tools from multiple locations
- Once confirmed, raise the TTL back to 3600 (1 hour) or higher
This pre-lowering technique is the standard practice for planned DNS changes (server migrations, hosting changes, domain transfers). It reduces propagation from “up to 48 hours” to “mostly done in 5 to 10 minutes.”
Factors That Affect Propagation Speed
TTL value: The biggest factor. Higher TTL = longer propagation. A TTL of 86400 (24 hours) means some resolvers won’t recheck for an entire day.
DNS provider: Some DNS providers have faster update mechanisms. Cloudflare, for example, updates their global network within seconds of a change.
ISP resolver behavior: Some ISP resolvers are poorly configured and may cache records longer than the TTL specifies (violating the RFC but it happens). Others aggressively flush caches.
Client-side caching: Your browser and OS also cache DNS. Even after global propagation, your local caches might still hold old data. ipconfig /flushdns on Windows or restarting your browser can help.
Common Scenarios
Migrating to a new host: Lower TTL, wait, update A record to new server IP, verify, raise TTL.
Setting up email (MX changes): Lower TTL on MX records first. Email providers usually recommend waiting 48 hours for MX propagation because some resolvers respect TTL loosely.
Changing nameservers: This is the slowest propagation because NS records are managed by the TLD registry, which may have its own propagation timeline. NS changes typically take 24 to 48 hours.
Adding a subdomain: Usually fast because there’s no old cached record to expire. The new subdomain should resolve within minutes of creation.
Test It Yourself
Check DNS Propagation
Look up any domain's DNS records from our servers. See if your changes have propagated.