DNS Propagation Explained: Why Changes Take Time

You updated your DNS records, refreshed your browser, and… nothing. Your old site is still there. Or worse, it works for you but a customer in another country still sees the old version. This is DNS propagation, and while it feels like something is broken, it’s actually the internet working exactly as designed.

This guide explains what DNS propagation really is, why different people see different results, how TTL controls the wait, and how to make your next DNS change almost painless.

What DNS propagation really means

DNS (the Domain Name System) translates a domain like hostreta.com/ into the IP address of the server that hosts it. When you change a DNS record — for example, pointing your domain to a new host — you update it at your DNS provider. That part is instant.

The delay comes from everywhere else. To keep the internet fast, DNS answers are cached by thousands of systems along the way:

• Recursive resolvers run by internet providers, mobile networks, and public services like Google DNS or Cloudflare DNS.
• Your operating system, which keeps its own small DNS cache.
• Your browser, which caches lookups too.

Each of these keeps the old answer until it expires. “Propagation” is simply the time it takes for all those cached copies to expire and be replaced with your new record. Nothing is actively “spreading” across the internet — old answers are just timing out one by one.

Why some visitors see the old site

Because every resolver cached your record at a different moment, they all expire at different moments. That’s why, during a change:

• You might see the new site on your phone (mobile network resolver) but the old one on your laptop (home internet resolver).
• A visitor in another country might see the old site for hours after you see the new one.
• Emails may briefly arrive at the old mail server if you changed MX records.

This is normal. The important thing during a migration is to keep the old server running until propagation is complete, so nobody lands on a dead site. And before any big change, take a fresh backup — see Website Backups: The 3-2-1 Rule Explained.

How TTL controls the wait

Every DNS record has a TTL (Time To Live), measured in seconds. It tells resolvers how long they may cache the answer before asking again.

• TTL 300 = 5 minutes. Changes are picked up quickly.
• TTL 3600 = 1 hour. A common default.
• TTL 86400 = 24 hours. Fewer lookups, but slow changes.

Here’s the key insight: the TTL that matters is the one that was set before your change. If your record had a 24-hour TTL, some resolvers will keep the old answer for up to 24 hours, no matter what you change now.

That’s where the famous “up to 48 hours” warning comes from. In practice, most changes are visible within minutes to a few hours — but a long old TTL, or a resolver that ignores TTLs, can stretch it out.

How to check propagation worldwide

Checking only from your own computer tells you very little. Use these methods instead:

1. Global DNS checkers such as whatsmydns.net or dnschecker.org query resolvers in many countries at once and show which ones return the new IP.
2. Command line: run nslookup yourdomain.com 8.8.8.8 (Google) and nslookup yourdomain.com 1.1.1.1 (Cloudflare) to compare major resolvers. On Mac or Linux, dig yourdomain.com +short works too.
3. Ask your authoritative nameserver directly with dig @ns1.yourdns.com yourdomain.com. If it shows the new record, your change is correct — everything else is just caching.

To see the new site on your own device sooner, flush your local cache: restart the browser, run ipconfig /flushdns on Windows, or switch to a different network (for example, your phone’s mobile data).

Speeding up your next DNS change

You can’t force resolvers worldwide to forget your record, but you can plan so the wait is tiny:

1. Lower the TTL a day ahead. At least 24 hours before the change, set the TTL on the records you’ll edit to 300 seconds. Wait for the old TTL to expire.
2. Make the change. Because resolvers now cache for only 5 minutes, most visitors switch over almost immediately.
3. Keep the old server live for at least a day or two, just in case.
4. Raise the TTL back (for example, to 3600) once everything is stable.

Changing nameservers (not just records) usually takes longer, because the registry’s own TTL for nameserver records is often 24–48 hours. If you can, change individual records instead of the nameservers. Using Cloudflare? Read Cloudflare Free vs Pro: Is Upgrading Worth It?.

Key takeaways

• DNS propagation is cached answers expiring, not records “spreading.”
• The old TTL decides how long the wait can be.
• Lower your TTL to 300 seconds a day before big changes.
• Check from several locations and resolvers, not just your own computer.
• Keep the old server running until the switch is complete.