How Long Does DNS Propagation Really Take? What Decides the Wait, and a Launch-Day Plan That Keeps It Short

Key takeaways

• "Propagation" is really caching. DNS does not push changes around the world. Resolvers keep an answer for a set time, then ask again, and the wait is the time left on that clock.
• The clock is the TTL. TTL (time to live) is a number of seconds on each DNS record. A change to a record with a 300 second TTL should be seen within about five minutes by resolvers that honour it.
• Nameserver changes are the slow case. Namecheap says a nameserver update can take 24 to 48 hours to take effect.
• Lower the TTL before the switch, not after. Wait at least as long as the old TTL, then make the change.
• Never change mail records without a copy. A missed MX record can lose email, so list them before you move anything.
• Waiting longer does not fix a mistake. If the authoritative answer is wrong, no amount of waiting helps.

The short answer

How long DNS takes to update depends on the record's TTL and on which resolver your visitor uses. If you change an A record that has a TTL of one hour, most visitors see the new address within an hour. If you change nameservers, expect longer: Namecheap says up to 24 to 48 hours. The way to shorten it is to lower the TTL to something like 300 seconds a day or two before the switch, wait for the old TTL to run out, then make the change and keep the old server running until you have checked.

Who is writing: Amariq builds and launches websites, and moved its own domain's DNS when amariq.com left Webflow. We haven't run a timing test for this post, so no time here is something we measured. Every figure comes from a help page or write-up linked in the text.

What ranks for this search, and what it leaves out

On 8 November 2026 the first page of Google (US, English) for "how long does dns propagation take" showed a Reddit thread, the whatsmydns.net checker, a 2017 Tiger Computing article called "The Myth of DNS Propagation", Openprovider, a Cloudflare Community answer, GoDaddy and Namecheap help pages, Network Solutions (19 November 2025) and CaptainDNS (26 March 2026, updated 29 October 2026). The answers split into two camps. The registrars say "a few hours to 48 or 72 hours". The two technical write-ups say that figure is a myth and the real wait is the TTL.

Both are partly right, and neither gives a small business owner a plan. The registrar pages tell you to wait. The technical pages assume you know what a resolver is. This guide connects the two: what the wait is, which changes are fast and slow, and what to do on the day.

What "propagation" actually is

Tiger Computing explains it plainly. DNS maps names to addresses, and the servers that answer are organised in layers. Lookups are cached along the way, because the root servers could not cope if every lookup went all the way up. Each record carries a time to live, in seconds, which tells other servers how long they may remember the answer.

CaptainDNS puts the consequence bluntly: DNS has no mechanism for broadcasting a change. When you change a record, resolvers that still hold the old answer keep serving it until their stored copy expires, then they ask again and get the new one. So the "propagation delay" is the time left on caches that were filled before your change.

Namecheap's help page describes the same effect from the registrar side: ISP servers around the world update their caches at different times, so some visitors reach your old server while others reach the new one.

Which changes are fast and which are slow

The last row catches people out. If a visitor or tool looked for a name before you created it, the resolver may remember "this does not exist" for a while. CaptainDNS explains that this timer is also set in the zone, and its sample shows 300 seconds.

What TTL values really mean

CaptainDNS gives a table of the worst-case wait for common TTLs, assuming a resolver cached the old answer just before you changed it:

On Cloudflare, per its documentation, proxied records have a TTL of "Auto" fixed at 300 seconds, and for DNS-only records you can choose a TTL between 60 seconds and one day (30 seconds on Enterprise). Cloudflare also says it may take longer than five minutes for you to see a change, because your own local cache may take longer to update.

Two caveats from CaptainDNS: some resolvers apply a minimum TTL (it says Google Public DNS uses 30 seconds), and some ISP resolvers cache for longer than the TTL even though they should not. Tiger Computing says the same about ISPs that cache for long periods whatever the TTL. You can't control those, so keep the old server working for a day or two after the switch.

Why you can still see the old site after a change

Even when the TTL has expired, you may see old content for reasons that have nothing to do with the record:

1. Your own device remembers. Browsers and operating systems keep short caches.
2. A different resolver. A resolver that cached the old answer later than another will keep it later.
3. A CDN or host cache. The page itself can be cached somewhere else.
4. A mistake. The change was not saved, or the wrong record was edited. CaptainDNS lists this as the most common cause and says to query the authoritative nameserver directly to check.

If you have waited longer than the TTL and still see the old answer, stop waiting and check the record at the source.

A launch-day plan

This is our summary of the steps both technical sources describe. It suits an A record or CNAME change, such as pointing a domain at a new website host.

1. Find the current TTL for the record in your DNS panel.
2. Lower it to 300 seconds at least as long before the switch as the old TTL. Tiger Computing's example reduces a one-day TTL a couple of days ahead. Do not change the address yet.
3. Wait for the old TTL to run out. Resolvers that cached the old TTL will not see the lower one until their copy expires.
4. Check the new host is ready. The site should load correctly on the new server before anyone is sent there.
5. Change the record to the new address. Keep the TTL low.
6. Check from more than one place. Ask the authoritative nameserver, then two or three public resolvers, as CaptainDNS shows with dig. A web checker such as whatsmydns.net also queries many locations.
7. Test the site, forms and email at the new address.
8. Keep the old server running for a day or two, in case some resolvers still send visitors there.
9. Raise the TTL again. CaptainDNS suggests 3,600 seconds as a balance. A permanently very low TTL means more lookups.

Changing nameservers

Nameserver changes are slower and affect the whole domain, including email. Namecheap offers a way to reduce the gap if you have not changed them yet: point the domain at the destination address with an A record at the current DNS provider, with a TTL of around 300 seconds, wait up to 30 minutes, then change the nameservers. Visitors then reach the new site whichever set of nameservers they still use. The same page warns that you can check the new site early by editing your own hosts file, but that only you will see it, and the entry should be removed once the change has settled.

Protect your email first

Before you move DNS, copy every record, especially MX and TXT records for mail, to the new provider. Our post on moving a site from Webflow to Cloudflare, what we learned moving Amariq, lists the mail records to check first. Our business email cost guide explains which provider holds your mail, and our guide to custom domains on Framer shows the records a site builder asks for.

How to check whether the change has arrived

Namecheap says there is no definitive way to tell when propagation is complete for you, since it depends on TTL, your ISP and your location.

What does not help

CaptainDNS lists three things that do not fix a slow change: restarting your router, switching your own resolver (it may make the change look finished for you but does nothing for other visitors) and simply waiting longer when the record is wrong. Clearing your own caches is worth doing, but it affects only your device.

Moving a domain between registrars is a separate job from changing DNS; see how to transfer a domain name without downtime.

Not sure what an A, CNAME, MX or TXT record does? Our plain guide to DNS records explains each one.

How Amariq can help

If you are moving a domain or launching a site and want the DNS side handled, send us the domain and where it should point and we will list every record, plan the TTL change and the order of steps, and check it after the switch. Nameserver changes and sign-ins stay in your hands: we prepare the exact values and you save them. We build on Webflow, Framer, WordPress, Shopify, Wix, Squarespace or a custom stack. Each project is priced from its scope, never by the hour, with 40% to start, 30% at design approval and 30% before launch. Once the final payment is made, the design, copy and code belong to you, and your domain, hosting and analytics accounts sit in your name. See our web design service or the website optimization service.

Frequently asked questions

How long does DNS propagation take?

It depends on the TTL of the record you changed. CaptainDNS says a record with a 300 second TTL is visible within about five minutes, and one with an 86,400 second TTL can take up to 24 hours. Namecheap says nameserver updates can take 24 to 48 hours.

Why do registrars say 24 to 48 hours?

It is a cautious figure for the slowest case, nameserver changes and long TTLs. CaptainDNS argues it dates from an earlier era of long default TTLs, and Tiger Computing says the cause is a TTL of 86,400 seconds, which is 24 hours.

Can I speed up DNS propagation?

You can't push a change to other people's resolvers. You can lower the TTL before you make the change, wait for the old TTL to expire, and then switch. You can also flush your own cache so you see the new answer sooner.

Why can I see the new site but my customer can't?

Your resolver and theirs cached the old answer at different times. Keep the old server working until you have checked from more than one place.

Will my email stop while DNS updates?

It can if mail records are missed or wrong. Copy every MX and TXT record before changing nameservers, and keep both mail systems working during a mail move.

Does changing nameservers take longer than changing an A record?

Generally yes. Namecheap quotes 24 to 48 hours for nameservers. A record change follows that record's own TTL.

Is there a tool to check DNS propagation?

Several, including whatsmydns.net, which appeared first on the results page. You can also ask resolvers directly with dig. Different results during a change are normal.