OxyPages

The DNS Propagation Time: How Long It Really Takes

The DNS Propagation Time: How Long It Really Takes

The DNS propagation time is set by one number you can read before you change anything. The three real waits, why 48 hours exists, and how to shorten it.

The OxyPages Team · · 9 min read

It's 10pm, the new site launches at 8am, and you've just changed one line in your domain's settings. You refresh. The old site is still there. You refresh again, and a help page somewhere tells you this can take up to 48 hours.

For the change you most likely made, it won't.

The DNS propagation time everyone quotes is the worst case for one specific kind of change, and it gets repeated as if it applied to all of them. The real wait is set by a number you can read before you touch anything: the TTL on the record you're replacing. Know that number and you can predict the wait to within a few minutes. You can even shorten it in advance.

This post is only about the timing. If you need the whole setup from scratch, the full guide to connecting a domain covers that. This picks up from the moment you press save.

TL;DR: Nothing actually propagates. Every DNS answer carries a TTL, the number of seconds anyone may cache it, and your wait is the old answer's TTL running out in caches you don't control. A new record on an unused name usually works within minutes. Editing an existing record takes up to the old TTL, often 5 minutes to an hour. Changing nameservers is the slow one, because on a .com the registry's record of which nameservers you use is cached for 172,800 seconds, exactly 48 hours. Lower the TTL a day before you change anything and the wait shrinks to minutes.

What Is DNS Propagation, Really?

DNS propagation is the time it takes for cached copies of an old DNS answer to expire, so everyone starts getting the new one. Nothing is pushed out to the internet when you save. Your DNS provider changes its answer instantly. The delay is everyone else still holding the old one.

Here's the chain a visitor's request goes through before it reaches your DNS provider:

  1. Their browser checks its own short memory.
  2. Their device checks the operating system's cache.
  3. Their home router may keep a copy too.
  4. Their resolver, usually the ISP's or a public one like Google's 8.8.8.8, checks its cache.
  5. Only if every one of those comes up empty does anyone ask your DNS provider.

Each cache keeps an answer for as long as its TTL allows. The DNS specification, RFC 1035, defines TTL as the time a record may be cached before the source should be asked again.

So the old answer dies in different places at different times. That ragged edge is all "propagating" means.

How Long Is The DNS Propagation Time For Each Kind Of Change?

It depends on what you changed, not on your registrar or your luck. A brand new record is usually live within minutes. An edited record takes up to its old TTL. A nameserver change can take up to 48 hours on a .com, because that's how long the registry tells resolvers to cache it.

What you changedWho's still holding the old answerTypical waitWorst case
Added a record to a name that had noneResolvers that were recently told "no such name"Seconds to minutesYour provider's negative-cache time: usually minutes, up to about 3 hours
Edited an existing A or CNAME recordEvery cache that saw the old answer recentlyUnder the old TTLThe full old TTL: 5 minutes, an hour, or a day
Changed nameserversResolvers holding the old delegation from the registryHours48 hours on a .com, about an hour of registry caching on a .sg
Renewed the domain or edited contact detailsNobodyNoneNone. DNS didn't change

A Brand New Record

A new record on a name that never had one has no old answer to wait out. The one catch is negative caching: if anyone looked the name up before the record existed, their resolver remembers "doesn't exist" for a while.

Your DNS provider's zone settings decide how long. RFC 2308, the negative caching standard, suggests one to three hours, though many providers use less. So don't visit the new address until after you've added the record.

Editing An Existing Record

This is the one most people are in, and the worst case is printed in your dashboard's TTL column. Read it first.

Defaults vary a lot. Cloudflare's "Auto" setting is 300 seconds, five minutes. I've also opened registrar dashboards with records sitting at 14,400 seconds (four hours) and 86,400 (a full day) that nobody had touched in years.

Here's the subtle part. Lowering the TTL right before you edit does almost nothing, because caches already holding the old answer count down the old number. Lower it one full old TTL in advance.

Changing Nameservers

Nameserver changes are slow because the delegation, the record saying which company answers for your domain, lives at the registry, not with you. You can check this yourself with dig NS yourdomain.com @a.gtld-servers.net: the .com servers hand out that record with a TTL of 172,800 seconds. That's 48 hours to the minute, and it's where the famous warning comes from.

Some visitors switch within minutes, others hold the old delegation until it expires. On a .com, plan for the full two days, with identical records at both providers until it's over.

What Slows It Down Beyond The TTL?

What Slows It Down Beyond The TTL? - OxyPages

When a change takes longer than its TTL, something else is caching. Check these, most common first:

  • Your browser. Chrome keeps its own host cache. Paste chrome://net-internals/#dns into the address bar and press "Clear host cache".
  • Your computer. On Windows, run ipconfig /flushdns. On a Mac, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal.
  • Your ISP's resolver. You can't flush it. You can test around it by asking a public resolver like 8.8.8.8 directly, and if you use Google's, its Google Public DNS flush cache page drops a cached name.
  • Serve-stale. Some resolvers keep handing out an expired answer for a day or more if they can't reach your DNS provider at all. RFC 8767 suggests a cap of one to three days. It only bites if the old provider vanished mid-move.

If the TTL has run out everywhere and the answer is still wrong, it isn't a timing problem. Something is set up wrong, like a leftover old record on the same name.

How To Check DNS Propagation From Outside

To check propagation, ask resolvers that aren't yours. Your own browser is the worst witness you have, because it's sitting behind three caches you just learned about.

  1. Use a global DNS checker. The free sites that query dozens of resolvers worldwide show who has the new answer and who doesn't.
  2. Ask a public resolver directly. dig is a free command-line tool built into Mac and Linux. In a terminal, dig www.example.com @8.8.8.8 and dig www.example.com @1.1.1.1. On Windows, nslookup www.example.com 8.8.8.8 does the same job.
  3. Read the countdown. The number after the name in a dig answer is the seconds left before that resolver asks again. That's the remaining wait, for that resolver, as a literal number.
  4. Ask your DNS provider itself. Find its nameservers with dig NS example.com +short, then run dig www.example.com @ followed by one of them. If the answer is wrong there, waiting won't fix anything. The record is wrong.
  5. Test on a phone with wifi off. Mobile data uses a different resolver, so it's a quick second opinion.

If your provider's answer is right and the public resolvers are counting down, you're just early.

The Night Before A Launch, Hour By Hour

The Night Before A Launch, Hour By Hour - OxyPages

Here's how I'd walk a friend through it. Say she's a wedding photographer moving her portfolio off an old site builder onto a new static host. The launch email goes to three hundred past couples at 8am. It's 9:55pm.

  • 9:55pm. She opens her DNS settings and reads the current www record: a CNAME pointing at the old builder, TTL 3600. Her worst case is now a number. One hour.
  • 10:00pm. The new host's docs offer two routes: change nameservers, or edit one record. She doesn't touch the nameservers. That would put her launch on a 48-hour clock.
  • 10:02pm. She edits the www record in place to the new host's target. She doesn't delete it and add a new one, because the gap in between would get cached as "doesn't exist".
  • 10:05pm. dig www.herdomain.com @8.8.8.8 still shows the old target, with about 2,900 seconds left on the countdown. That's expected.
  • 10:15pm. Checking your DNS provider directly, the new host spots the record and issues her HTTPS certificate. Until then, a visitor reaching the new host would see a certificate warning. She doesn't need to buy one, and what an SSL certificate actually costs explains why.
  • 11:05pm. Both public resolvers return the new target. Her laptop still shows the old page, but that's the browser's saved copy, not DNS. A hard refresh shows the new site.
  • 11:10pm. She leaves the old builder site running until the next evening. Anyone stuck on a stale answer still sees a working page rather than an error.
  • 8:00am. The email goes out, nine hours after the old TTL ran out everywhere that plays by the rules.

Next time I'd have her lower that TTL to 300 the day before, turning one hour into five minutes. But one hour was fine, because she read the number instead of trusting "48 hours".

How To Plan A Change So Nobody Notices

The trick is to shrink the TTL before the change and keep the old site alive after it. Six steps:

  1. A day or two before, lower the TTL on the record you'll change to 300 seconds. Then wait at least one full old TTL.
  2. Test the new site on the host's own free address first, so DNS is the only thing left to change.
  3. Edit the record in place. Never delete and re-add.
  4. Keep the old site up for at least the old TTL. For a nameserver change, keep it up for two days.
  5. Verify from outside, using the checks above.
  6. Raise the TTL again to an hour or so once it's settled. That means fewer lookups and a little cover if your DNS provider has an outage.

What To Do Next

None of this is scary once you've read the TTL. Do that tonight, even if the move is weeks away.

If the new site isn't online yet, do that first. how to host a static website walks through it.

When the site is on OxyPages (custom domains are on paid plans), the change is one CNAME pointing at cname.myoxypages.com with any proxy switched off, and the domains page re-checks automatically. One limit to know: OxyPages doesn't host DNS, so that record and its TTL live at your registrar or DNS provider. If you'd rather have DNS and hosting in one dashboard, Cloudflare or Netlify will host both. Otherwise, publish your site and connect your domain when you're ready.

FAQ

Why Does My Site Work On My Phone But Not My Laptop?

Your laptop is still holding the old answer in its browser or system cache, while your phone on mobile data asked a different resolver. Clear both caches and try again. If 8.8.8.8 already shows the new answer, your setup is fine.

How Long Does A Nameserver Change Take On A .sg Domain?

Much less than on a .com. The .sg registry hands out its delegation records with a TTL of 3,600 seconds, one hour. The old provider's own records can still hold some resolvers longer, so give it a few hours, not two days.

Does My Registrar Make It Slower?

Only through the TTL it sets on your records, which you can usually change. Beyond that, your DNS propagation time is set by caches on the visitor's side, and no registrar controls those.

Try It Now

Still Here? Drop It In.

The whole pitch fits in one sentence: your HTML, on a link, in seconds.

Drag and drop your HTML files, a folder, a ZIP, your app's build folder, a PDF or an image

or ·

No account needed. Your unclaimed website stays live for 30 minutes on a free subdomain. Claim it to your account to keep it permanently.

  • No Account Needed
  • Free SSL
  • 30-Minute Unclaimed Link, Claim To Keep It