Long-exposure light trails on a motorway at night

Blog  /  Troubleshooting

How long does DNS propagation take?

Usually as long as the old record's TTL, and often far less than the 24 to 48 hours a support page will quote you. Here is what is happening while you wait, and how to tell whether the change has worked.

Nothing is actually propagating

"Propagation" suggests your new record is being pushed out across the internet, server by server. It isn't. When you press Save, your DNS provider updates its own nameservers, usually within seconds or minutes. Those nameservers are the only place your records live.

Everyone else gets a copy on request. When a visitor's device needs your address it asks a resolver, normally one run by their broadband or mobile provider, or a public service such as 1.1.1.1 or 8.8.8.8. The resolver asks your nameservers, passes the answer back and keeps a copy for as long as the record's TTL allows. Until that copy expires, it keeps handing out the old answer without checking again.

So the wait is thousands of separate caches, each running down its own clock. That is why a change can be live on your phone and stale on your laptop at the same moment. Both are behaving correctly.

Changing a record: wait out the old TTL

When you edit an existing A, CNAME, MX or TXT record, the longest you should have to wait is the TTL the record had before you changed it. If it was one hour, every well-behaved resolver has the new answer within the hour. If it was 14400 seconds, the cPanel default, allow four hours.

Two things follow from that:

  • Lowering the TTL after the change does not help. Caches already hold the old record with the old TTL. A lower TTL only speeds up the next change. See what TTL to set and when to lower it.
  • A brand-new name can still be delayed. If you looked up shop.yourdomain.com before the record existed, your resolver cached the "no such name" answer. How long it keeps that is set by the zone's SOA record: typically minutes, sometimes hours. Create the record first, then test.

A few providers also take time to publish an edit to their own nameservers, whatever the TTL. Our guides flag the slow ones: IONOS can take up to an hour, DreamHost can take longer, and Plesk holds edits until you press the button that applies them.

Changing nameservers: the slow one

Switching nameservers, for example to move your DNS to Cloudflare or to a new host, works differently. The list of nameservers for your domain is published by the registry that runs your domain's ending (.com, .co.uk, .org and so on), and the registry sets the TTL on it, not you. For .com that TTL is 48 hours.

This is where the "allow 24 to 48 hours" advice comes from, and for nameserver changes it is fair. Many visitors will reach the new nameservers far sooner, but some resolvers will keep asking the old ones for a day or two.

The practical rule: keep the old DNS zone in place, with correct records, until the switch has settled. If both sets of nameservers give the same answers, nobody notices the overlap. Our guide to moving a website without downtime covers the order to do it in.

How to check what the world sees

Your own computer is the worst place to test from, because your browser, your operating system and your router each keep a cache of their own. Ask a public resolver directly instead:

dig @1.1.1.1 yourdomain.com A
dig @8.8.8.8 yourdomain.com A

The number after the name in the answer is the TTL, counting down at that resolver. If you see the old value with 1200 left, it will refresh within 20 minutes. On Windows, nslookup yourdomain.com 1.1.1.1 gives you the answer without the countdown.

To confirm the change was saved at all, skip the caches and ask one of your own nameservers. Get their names with dig NS yourdomain.com +short, then:

dig @ns1.your-dns-provider.com yourdomain.com A +short

If that returns the new value, the change is made and the rest is waiting. If it returns the old value, the problem is not propagation. Most often you have edited a zone your nameservers do not point at. The "who runs my DNS?" lookup tells you which panel is the live one, and the Route Planner checks every record against live DNS in one click.

What you can and can't speed up

  • Your own machine. Flush the local cache with ipconfig /flushdns on Windows or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS, then test in a private browser window. Switching your phone to mobile data is a quick second opinion.
  • Public resolvers. Google Public DNS and Cloudflare's 1.1.1.1 each have a public page where you can ask them to drop their cached copy of a name. It helps people who use those resolvers and nobody else.
  • Everyone else. You cannot clear an internet provider's cache from outside. The TTL has to run down.

If the old TTL has passed, your nameservers give the right answer and public resolvers still disagree, stop waiting and look for a second cause. A leftover parking record, domain forwarding left switched on at the registrar and a duplicate record are the usual suspects. All three are on the troubleshooting page.

Keep reading

All posts