When you make a change to your domain’s nameservers or DNS records (A record, CNAME, MX, TXT), that change does not appear instantly everywhere on the internet. DNS servers around the world cache old information for a period defined by the TTL (Time to Live) setting. Propagation is the process of those caches expiring and fetching the updated record.
Why propagation happens
The internet has thousands of DNS resolvers (operated by ISPs, Google, Cloudflare, corporate networks, etc.). Each resolver caches DNS records to reduce lookup time. When you change a DNS record, each resolver keeps serving the old cached record until its TTL expires. As TTLs expire one by one across all resolvers, the change “propagates.”
Propagation timelines
| Change type | Typical propagation | Why |
|---|---|---|
| Nameserver change | 24–48 hours | Nameserver records have higher TTLs, cached at registry level |
| A record update | 15 minutes to 4 hours | TTL-dependent; modern TTLs often 300–3600 seconds |
| MX record update | 30 minutes to 4 hours | Similar to A record |
| CNAME update | 15 minutes to 1 hour | Lower TTL common for dynamic records |
| TXT record update | 15 minutes to 1 hour |
How TTL affects propagation speed
TTL is the number of seconds a DNS record should be cached before being refreshed. A TTL of 3600 means resolvers cache the record for 1 hour. A TTL of 300 means resolvers refresh it every 5 minutes.
Before making a planned change (e.g., migrating to a new host): reduce your TTL to 300 (5 minutes) 24–48 hours before the planned change. When you make the switch, propagation takes only 5–10 minutes instead of 4–24 hours.
After the change is stable: Raise the TTL back to 3600 (1 hour) or higher for better performance DNS lookups are faster when records are cached longer.
Why different users see different results during propagation
During propagation, a user in the US whose ISP’s resolver has cached the old IP address will see your old website. A user in Germany whose resolver has already refreshed will see your new website. This is normal and expected it is not a sign of an error.
To check propagation status from multiple geographic locations, use tools like:
- whatsmydns.net shows DNS record resolution from 20+ global locations
- dnschecker.org similar global check
- dig command (terminal) checks the DNS record directly from a specific DNS server
The domain transfer and propagation relationship
During a domain registrar transfer (e.g., moving from GoDaddy to Namecheap), your nameservers and DNS settings carry over automatically you do not need to reconfigure DNS after a transfer. The domain’s DNS records remain intact at the registry level throughout the transfer.
If you choose to update your nameservers after the transfer (e.g., to point to a different hosting provider), that nameserver change then triggers a 24–48 hour propagation period for the new nameservers to resolve globally.