When you change a DNS record — pointing your domain to a new server, updating nameservers, or adding a new email record — that change does not appear everywhere on the internet instantly. It has to spread out, gradually, to thousands of DNS servers around the world that each keep their own temporary copy of your domain's information. That spreading-out process is called propagation, and it typically takes anywhere from a few minutes to 48 hours.
This is normal. It is not a sign anything is broken. And there are a few things worth knowing that make the wait much less confusing.
Why This Happens: The Internet's Address Book Has Many Copies
Every time a device looks up your domain — a browser loading your site, an email server delivering a message — it asks a DNS server "where does this domain point to?" Constantly asking the original source for every single lookup, from every device, every time, would be incredibly slow. So instead, DNS servers around the world cache (temporarily store) the answer once they look it up, and reuse that stored answer for a while before checking again.
That "while" is controlled by a setting called TTL — Time To Live — attached to each DNS record. TTL tells every caching server: "you are allowed to remember this answer for this many seconds before you are required to check again."
Here is the part that catches people out: the TTL that matters is the one that was set before you made your change, not the new one. If your domain's A record had a TTL of 24 hours, and you change that A record right now, any DNS server that already cached the old answer in the last 24 hours will not check again until that window expires.
A Realistic Timeline
- Minutes: People near you, on the same ISP or network, with nothing cached yet, may see the change almost immediately
- A few hours: Most of the world typically catches up within this window
- Up to 24–48 hours: Some resolvers, especially larger corporate networks or certain ISPs, hold onto cached records longer regardless of TTL
- Nameserver changes (switching which company manages your DNS entirely) tend to take longer than single-record changes
If it has been more than 48 hours and a record still has not updated everywhere, that is the point where it is worth investigating further.
What You Can Do While Waiting
- Check propagation status. Our free DNS propagation checker asks your domain’s own nameservers for the correct answer, then shows which major DNS providers already have it and how long the rest have left on their cache. It will not speed anything up, but it removes the guesswork.
- Clear your own device's DNS cache. Your own computer and browser also cache DNS answers locally. If everyone else seems to see the new site but you don't, your own machine may just be holding onto an old cached answer. Here is how to flush your DNS cache on Windows, Mac, browsers and phones.
- Avoid making further changes while waiting. Changing the record again resets the clock and can extend the confusion, since now there are multiple "versions" cached at different servers at different times.
- For email specifically, expect a longer effective wait. Mail servers often only check DNS at the point they are about to send a message, and many queue and retry over several hours if delivery fails. Email-related DNS changes (MX records) can feel like they are taking even longer because of how mail delivery retry logic works.
How to Check DNS Propagation Yourself
The quickest way is our free DNS propagation checker: enter your domain, pick the record type, and it compares your nameservers’ answer with Google, Cloudflare, Quad9, OpenDNS and other major providers — including how long each one has left before it refreshes.
If you prefer the command line, you can ask specific DNS servers directly:
# Ask Google's resolver for your A record (Windows, Mac or Linux)
nslookup -type=A example.co.uk 8.8.8.8
# Ask Cloudflare's resolver, short output (Mac / Linux)
dig @1.1.1.1 example.co.uk A +short
# Find your nameservers, then ask one directly for the "source of truth"
dig example.co.uk NS +short
dig @ns1.yournameserver.com example.co.uk A +shortIf your nameservers already return the new value but a resolver doesn’t, that resolver is still serving its cached copy — it will update once the record’s TTL runs out. Not sure which record to check? See DNS records explained.
Lowering TTL Before a Planned Change
If you know in advance that you will be migrating servers, changing nameservers, or moving to a new email provider, the single most useful thing you can do is lower the TTL on the relevant records a day or two beforehand. Setting TTL down to 300 seconds (5 minutes) well ahead of the actual change means that by the time you make the real change, caching servers are already only holding answers for a few minutes at a time — and propagation of the actual change afterwards will be dramatically faster. For the details and sensible values, read what TTL is and what to set it to.
When to Contact Support
- It has been more than 48 hours and the change still is not visible from multiple global locations (not just your own device)
- Email has stopped working entirely after an MX record change
- You are planning a migration and want TTL lowered in advance to minimise downtime
Frequently Asked Questions
Can I make DNS propagation happen faster?
Not after the fact. Propagation speed is governed by TTL values that were set before the change, and by individual ISPs' caching behaviour. The only real lever is lowering TTL in advance of a planned change.
Why does the new site work on my phone but not my laptop?
Different devices and networks query different DNS resolvers, each with their own cache and timing. It is completely normal for propagation to reach one network before another.
I changed my nameservers — how long until that is done?
Nameserver changes are usually the slowest type of DNS change to propagate fully, often taking the full 24–48 hour window, because the lookup chain itself is cached at multiple levels including sometimes at the domain registry. Our step-by-step guide covers how to change nameservers safely.
How do I check whether DNS has propagated?
Use a DNS propagation checker to compare the answer from your own nameservers with major public resolvers. When they all match, propagation is effectively complete — anything still wrong on your own device is a local cache you can flush.
Check DNS propagation now Find a domain Need help? Contact support
