How Long Does DNS Propagation Take? (and Why You See the Old Site)
How long does DNS propagation take? Usually minutes to a few hours, occasionally up to 48 — and until it finishes, some people (often you) keep seeing the old website or the old email server.
Common signs of this issue
- You changed DNS and are asking how long does DNS propagation take, because the new site is not showing yet.
- You moved to a new host and your computer still shows the old website, while a friend or your phone shows the new one.
- A free DNS checker shows a mix of old and new addresses in different countries.
- Email stops or starts arriving in two places after a change to MX records or nameservers.
- Your registrar says the change is saved, but nothing looks different hours later.
- The new site works on mobile data but not on your office Wi-Fi, or the other way around.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Work out what kind of change you made. Editing a single record (an A record, CNAME, or MX record) at your current DNS provider is usually quick. Changing nameservers — moving DNS to a new company altogether — is slower, because the domain's registry has to hand out the new nameserver list and older answers can be cached for up to 48 hours.
- Find the TTL (time to live) next to the record in your DNS settings. It is the number of seconds other servers may cache the old answer: 3600 means one hour, 86400 means a day. That old TTL, not the new one, sets how long the previous answer can linger.
- Search for a free DNS propagation checker, enter your domain, choose the record type (A for the website, MX for email), and look at the results from around the world. If most locations show the new value, the change is working and the stragglers will catch up.
- Test from a different network: your phone with Wi-Fi turned off, or a device at home. If the new site shows there, the issue is caching on your own computer or office network, not the DNS change itself.
- Flush your own computer's cache. On Windows, open Command Prompt and run
ipconfig /flushdns. On a Mac, open Terminal and runsudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. In Chrome you can also visitchrome://net-internals/#dnsand click Clear host cache, then close and reopen the browser. - If you use a public resolver such as Google (8.8.8.8) or Cloudflare (1.1.1.1), both offer a free purge cache page where you can ask them to refresh one domain. Search for "Google Public DNS flush cache" or "Cloudflare 1.1.1.1 purge cache".
- Rule out ordinary caching. If DNS already points to the new server everywhere but you still see old content, it is likely browser or site caching instead — see website changes not showing.
- For a planned move, lower the TTL on the records you will change to 300 seconds (five minutes) a day or two ahead. When you make the real change, the old answer then expires in minutes instead of hours.
What this usually means
"Propagation" is a slightly misleading word. Your change does not travel outward across the internet; it is saved instantly at your DNS provider. What takes time is everyone else's caches expiring. Internet providers, office routers, and your own computer remember the last answer they got for your domain so they do not have to ask every time, and they keep that answer until its TTL runs out. Until then, they keep sending people to the old address — which is why the change looks finished for some people and not others, as described in website down for some users.
For a simple record change with a typical one-hour TTL, most people see the new site within an hour or two. Nameserver changes are slower because two layers of caching are involved: the registry's record of which nameservers your domain uses, and the records on those nameservers. Up to 24 to 48 hours for the last stragglers is normal there. One trap catches people often: if you looked up a brand-new record before it existed, some resolvers cache the "doesn't exist" answer for a while too, so checking too early can make the wait feel longer.
If a global checker still shows the old value everywhere after the TTL has passed, it is not propagation — the change probably was not saved, was made at the wrong company, or is being overridden. A classic cause is editing records at the registrar while the domain's nameservers actually point to a host or Cloudflare, so the edits are never used. Check which nameservers your domain uses and make changes there; how to point a domain to your website explains nameservers versus records.
What not to do
- Don't keep changing the records while you wait. Each new change adds another round of caching and makes the mixed results last longer.
- Don't cancel your old hosting the moment you change DNS. Keep it running for at least a few days so visitors who still reach it get a working site.
- Don't judge the result only from your own browser. Your computer is often the last place to update.
- Don't change nameservers without first copying every existing record, especially MX, SPF, and DKIM records for email.
- Don't pay for a service that promises to "speed up propagation". Nobody can force other networks to drop their caches early.
- Don't set extremely long TTLs, such as a week, on records you might need to change in a hurry.
When to get help
Waiting is the answer most of the time, but not always. If the checker still shows the old value everywhere a day later, if email broke when the nameservers changed, or if you are not sure which company actually controls your DNS, the problem is a wrong or missing record rather than time. That is also true during a host move with a live shop or booking system, where every hour of visitors hitting the old server means lost orders or double bookings. Someone experienced can read the actual DNS answers, spot the misplaced record in minutes, and plan the cutover so the website and email switch cleanly.
Glenn at WebsiteSelfHelp sorts out stuck DNS changes and messy host moves for small businesses. Send him the domain and what you changed, and he will tell you whether it just needs time or needs fixing, and what it would take to put right — no logins required to get an answer.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Frequently asked questions
How long does DNS propagation take?
For a normal record change, usually minutes to a couple of hours, depending on the old TTL. Nameserver changes can take up to 24 to 48 hours to reach everyone. Your own computer is often the last to update.
Why do I still see my old website after changing DNS?
Your computer, router, or internet provider is still using a cached copy of the old address. Flush your DNS cache, try your phone on mobile data, and check a global DNS checker to see the real state.
Can I speed up DNS propagation?
You can only influence it ahead of time by lowering the TTL a day or two before the change. After the change, you can flush your own cache and ask Google or Cloudflare public DNS to refresh, but you cannot clear other networks' caches.
Is a nameserver change slower than changing an A record?
Usually, yes. Nameserver changes go through the domain registry, and those answers are often cached for up to 48 hours. Changing a record at your existing DNS provider only waits on that record's TTL.
Will DNS propagation affect my email?
It can. If MX records or nameservers change, some mail may reach the old server for a while. Keep the old mailbox running until the checker shows the new MX records everywhere, then check it one last time.
Does DNS propagation hurt my Google rankings?
Not if both the old and new servers serve the same working site during the switch. It only causes trouble if one of them is broken or cancelled while Google is still being sent there.
It has been 48 hours and nothing changed. Is it still propagating?
Almost certainly not. After that long, the record is probably wrong, saved at a company that is not your active DNS provider, or overridden by another setting. Check which nameservers your domain uses and look there.