Hosting · Explainer
How Long Does DNS Propagation Take?
Short answer
DNS propagation usually takes minutes to a few hours for a record edit, and up to 48 hours for a nameserver change. The wait is set by the record's old TTL, the timer that tells resolvers how long to cache the old answer. Once that timer runs out, resolvers fetch the new value, so lowering the TTL before a planned change is the fastest way to shorten the wait.
Key takeaways
- Most DNS record edits reach users within minutes to a few hours, while nameserver changes can take up to 48 hours.
- The old TTL sets the wait: a resolver keeps the old answer until the old timer runs out.
- Lower the TTL to 300 seconds at least one old TTL period before a planned move.
- A new record has no old cache, so it often works within minutes of being added.
- After 48 hours with no change, the cause is usually a wrong record or nameserver, not delay.
What is DNS propagation?
DNS propagation is the time it takes for DNS resolvers around the world to stop serving a cached old record and start serving your new one.
Nothing actually travels from server to server. When you edit a record, your authoritative nameserver answers with the new value at once. Each resolver keeps the old answer until its saved copy expires, then asks again and gets the new one.
That is why two visitors can see different sites at the same moment. One resolver has already refreshed, and the other still holds the old record. Google Cloud's Cloud DNS overview explains the same two-step process: first the change reaches the authoritative servers, then resolvers pick it up when their cache expires.
How long does DNS propagation take?
Most record edits reach most users within minutes to a few hours, while nameserver changes can take up to 48 hours.
The exact wait depends on the old TTL, the type of change, and how each resolver caches. GoDaddy's help page on propagation puts it plainly: most DNS changes propagate within a few hours, but you should allow up to 48 hours for everything to update.
Plan for the slow case, not the fast one. If you move a live WordPress site, back it up first and tell visitors and staff that some people may see the old site for up to 2 days. See how to back up WordPress before you start a move.
What is TTL and how does it control propagation time?
TTL, or time to live, is a number in seconds on each DNS record that tells resolvers how long they may cache it.
A TTL of 3600 means resolvers can serve the old answer for up to 1 hour after your change. A TTL of 86400 means up to 24 hours. Google Cloud's Cloud DNS overview uses the same example: a TTL of 86400 instructs resolvers to cache the record for 24 hours.
The old TTL sets the wait, not the new one. A resolver that cached your record just before you edited it keeps the old value for the full old TTL. Lowering the TTL only helps if you do it at least one old TTL period before the change.
| TTL in seconds | Plain time | When it fits |
|---|---|---|
| 60 | 1 minute | Just before a planned change |
| 300 | 5 minutes | A common short value for moving day |
| 3600 | 1 hour | A normal everyday value for many sites |
| 86400 | 1 day | Records that almost never change |
Cloudflare's TTL docs say DNS-only records can use a TTL from 60 seconds to 1 day on non-Enterprise plans, or 30 seconds on Enterprise plans. Proxied records use an Auto TTL of 300 seconds, and you cannot edit that value.
How long do different DNS changes take?
A record edit takes about one old TTL, a nameserver change takes 24 to 48 hours, and a brand-new record shows up in minutes.
| Change | Typical wait | Why |
|---|---|---|
| A or AAAA record edit | One old TTL, often minutes to a few hours | Resolvers cache the old answer until the TTL ends |
| CNAME, MX or TXT edit | One old TTL | Same caching rule as any other record |
| Nameserver change | 24 to 48 hours, rarely 72 hours | The registry delegation must update, and old NS answers carry long TTLs |
| Brand-new record | Minutes | No old copy exists in any cache |
Namecheap's propagation guide says a nameserver change takes 24 to 48 hours, and in rare cases up to 72 hours. The same guide says switching between Namecheap's own DNS services usually takes effect within 1 hour, or 24 hours in rare cases.
A new record has no old copy in any cache, so resolvers fetch it fresh on the first lookup. That is why a new subdomain often works at once while an edited record lags behind.
Why do nameserver changes take longer than record edits?
Nameserver changes add an extra step at the registry, and the old nameserver answer carries a long TTL.
When you change nameservers, the registry that runs your domain extension must publish the new delegation. Resolvers that cached the old delegation keep using the old nameservers until that cache expires. Cloudflare's migration guide notes that DS record TTLs are typically 24 hours, or 86400 seconds.
Your new DNS host must already hold a full copy of your records before you switch. If a record is missing there, visitors get errors instead of the old site once resolvers move over. Check the cost and renewal terms of your domain before a move in how much a domain name costs.
How can you speed up DNS propagation before a move?
Lower the TTL on the records you plan to change to 300 seconds at least one old TTL period before the move.
- Check the current TTL on each record you will change.
- Set the TTL to 300 seconds (5 minutes).
- Wait out the old TTL so resolvers pick up the short value.
- Make the change, confirm it, then raise the TTL back.
Cloudflare's migration guide recommends lowering TTLs 24 to 48 hours before a planned move, or longer to match your longest current TTL, with 300 seconds as a common short value.
Namecheap's propagation guide gives the same idea as a concrete trick: point an A record at the new IP with a 300-second TTL, wait up to 30 minutes, then change the nameservers.
After the move settles, raise the TTL back to a normal value such as 3600 seconds. Short TTLs mean more lookups, so they are a tool for moving day, not a permanent setting. If your DNS runs on Cloudflare, compare the plans in Cloudflare free vs Pro for WordPress.
How do you check if your DNS change has propagated?
Query your authoritative nameserver directly with dig, then compare the answer from public resolvers such as Google's 8.8.8.8 and Cloudflare's 1.1.1.1.
- Ask your authoritative nameserver first:
dig yourdomain.com @your-nameserver - Ask a public resolver:
dig yourdomain.com @8.8.8.8 - Ask a second public resolver:
dig yourdomain.com @1.1.1.1 - Repeat the checks over a few hours and note which resolvers have flipped.
Google Cloud's monitoring docs say to use the watch and dig commands, and that your authoritative nameserver should show the change within 120 seconds. If the authoritative server still shows the old value after that, the change did not save.
Online propagation checkers query the same record from many locations at once. They show a map, not a verdict: a few slow resolvers do not mean the change failed. If you are moving hosts at the same time, read how to choose WordPress hosting so the new server is ready before you switch DNS.
Why does your site still show the old version after a DNS change?
The most likely cause is a cached old record at your ISP, your device, or your browser, not a failed change.
Several caches sit between you and the new record. Your computer, your router, and your ISP can each hold the old answer. Your browser can also cache the page itself, which looks the same as a DNS delay.
Check from another network, such as mobile data, to separate a local cache problem from a real DNS problem. If mobile data shows the new site and your home Wi-Fi shows the old one, the wait is in your local cache.
Clearing the browser cache is a separate step from DNS. It helps when the page itself is cached, and it is one of the steps in how to speed up WordPress.
What should you do if DNS has not propagated after 48 hours?
After 48 hours, treat it as a configuration error, not a delay, and check the records themselves.
- Confirm the nameservers at your registrar match your DNS host.
- Check the record value and TTL for typos.
- Query the authoritative nameserver directly with dig.
- Ask your DNS host or registrar support to check the zone.
GoDaddy's help page on propagation says the same thing: if it has been more than 48 hours and changes are not showing, there may be a different cause, such as incorrect DNS settings.
What mistakes should you avoid?
The most common mistakes are switching nameservers too early, lowering the TTL too late, and trusting a single device to judge propagation.
- Changing nameservers before the new DNS host has a full copy of your records.
- Lowering the TTL at the same time as the change, instead of at least one old TTL period before it.
- Judging propagation from one device on one network.
- Editing the wrong zone when a domain has DNS at two providers.
- Forgetting email records such as MX, SPF and DKIM during a move.
- Treating a browser cache as a DNS problem and waiting for a fix that never comes.
Frequently asked questions
Does DNS propagation affect email?
Yes. MX, SPF and DKIM records follow the same TTL rules as any other record, so mail servers can keep using the old mail host until the old TTL runs out. When you move email, lower the TTL on the mail records days before the switch, and allow up to 48 hours before you call it a problem.
Can I speed up propagation after I already made the change?
No. Once the change is saved, the old TTL governs how long resolvers keep the old answer, and you cannot recall those cached copies. Flushing the DNS cache on your own computer helps only your own device. Everyone else has to wait out the old TTL.
Do I need to wait 48 hours before my WordPress site works?
No. Most visitors see a record edit within minutes to a few hours, and a brand-new domain often works within minutes. The 48-hour figure is a safe ceiling for nameserver changes, not the usual wait. Check with dig against a public resolver to see the real state.
Does changing nameservers change my DNS records?
Yes, in effect. The new nameservers become the source of truth for your domain, so their zone replaces the old one. Copy every record, including email records, to the new DNS host before you switch, or mail and subdomains can break.
Why do some visitors see the new site and others see the old one?
Each resolver cached the old record at a different time, so each one expires at a different time. A visitor whose resolver refreshed early sees the new site, while a visitor whose resolver cached the old answer minutes before your change waits out the full old TTL.
Sources
- Time to Live (TTL) Cloudflare Docs
- Cloud DNS overview Google Cloud Documentation
- Use logging and monitoring Google Cloud Documentation
- What factors affect DNS propagation time? GoDaddy Help
- DNS Propagation - Explained Namecheap Knowledge Base
- Phase 2: Preparation Cloudflare Docs
- CloudFlare DNS is simple, fast and flexible Cloudflare Blog
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
