Your domain hasn’t updated everywhere because computers around the world are still using a saved copy of your old DNS settings. Each copy expires after a set time, called the TTL, and then fetches the new answer. Most record changes show up within minutes to a few hours, while nameserver changes can take up to a day. Changing things again while you wait usually makes it slower, not faster.
Key takeaways
- “Propagation” is really old answers expiring from caches, not your change travelling the world.
- The TTL on each DNS record sets how long other systems may keep the old answer.
- Lower the TTL a day before a planned move, so the switch-over is quick.
- Check progress with a public lookup tool, not just your own browser.
- Don’t flip settings back and forth. Every change restarts the wait.
What is DNS propagation?
DNS is the internet’s address book. When someone types your domain, their device asks a DNS resolver (usually run by their internet provider, or a public one like Google’s) where to find your website and email. The resolver asks your DNS host, then saves the answer so it doesn’t have to ask again for every visitor.
That saved answer is the reason changes seem slow. When you update a record, your DNS host has the new answer straight away. But thousands of resolvers still hold the old one until it expires. “Propagation” is simply that period while old copies run out, one resolver at a time.
How long does DNS propagation take?
It depends on two things: the TTL on the record you changed, and what you changed.
- Ordinary records (A, CNAME, MX, TXT) follow their TTL. A record with a 300-second TTL clears in about five minutes. One set to a day can take a day. Cloudflare notes that “a longer TTL also means that updates to your records take longer to go into effect” (Cloudflare).
- Nameserver changes move your whole DNS to a new provider, which goes through the domain registry. Cloudflare tells customers to allow up to 24 hours (Cloudflare).
Some resolvers cap how long they keep records. Google Public DNS, for example, generally limits cached records to six hours even when the TTL is longer (Google Public DNS). Your own computer and browser keep copies too, which is why you may be the last to see your change.
How do I check DNS propagation?
- Confirm the change saved. Log in to your DNS host and check the record is exactly right. A typo looks just like slow propagation.
- Ask from outside your network. Use Google Admin Toolbox Dig or a global propagation checker. If most locations show the new value, it’s working.
- Test on mobile data. Turn off wi-fi on your phone and load the site. That uses a different resolver from your office.
- Clear your own cache. Restart your browser, or your computer, before deciding nothing has changed.
- Wait out the TTL. If the old TTL was 4 hours, give it 4 hours before you worry.
If you use Google Public DNS, its Flush Cache tool can refresh a record early. After a nameserver change, Google advises flushing the main domain before any subdomains.
What makes DNS problems worse?
In our experience, most “propagation problems” are made worse by the fix. Common ones:
- Changing it back. Now some resolvers hold the old answer, some the new, and some the one in between.
- Editing records at the wrong provider. If your nameservers point to Cloudflare, changes at your registrar do nothing. Check where your DNS is actually hosted first.
- Forgetting email records. Moving nameservers without copying MX, SPF and DKIM records stops email. Our guide to SPF, DKIM and DMARC explains what those records do.
- Cancelling the old host too early. Keep the old server running for a few days, so stragglers still reach a working site.
If you can’t even log in to change your DNS, the domain may be registered to someone else. Our article on who owns my domain shows how to check.
How do I avoid the wait next time?
Plan the change a day ahead. Lower the TTL on the records you’ll change to five minutes, then wait at least as long as the old TTL. When you make the real change, resolvers pick it up within minutes. Raise the TTL again once everything works.
This is how we handle a free website migration: lower TTLs, copy every record, switch, then check from several locations before the old host is cancelled. Our domain and DNS management includes the same care for everyday record changes. If your domains are scattered across providers, you can also register your domain with WMS and keep the records in one place.
Frequently asked questions
Why does my website show the new host for me but not my client?
You’re using different DNS resolvers. Yours has fetched the new answer, while theirs still holds the old one until its TTL expires. It usually sorts itself out within hours. Ask them to restart their browser or try mobile data.
Can I speed up DNS propagation?
Not once the change is made, except by flushing specific public resolvers such as Google Public DNS. The real speed-up comes beforehand: lower the TTL a day early so the old answer expires quickly when you switch.
Does DNS propagation really take 48 hours?
Rarely these days. Most record changes clear within minutes to a few hours, depending on the TTL. Nameserver changes can take up to a day. Hosts often quote 48 hours to be safe.
Will my email stop working during propagation?
Not if your MX records stay the same or are copied exactly to the new DNS host. Email breaks when those records are left behind during a nameserver change, not because of propagation itself.
What TTL should I use?
For everyday use, an hour to a few hours is sensible. Drop it to five minutes the day before a planned change, then put it back afterwards.
Sources
- Time to Live (TTL), Cloudflare Docs
- Change your nameservers (full setup), Cloudflare Docs
- Google Public DNS frequently asked questions, Google for Developers
- Dig, Google Admin Toolbox