DNS propagation: why changes take time

Why DNS changes don't take effect instantly, how long propagation takes, and what to do while you wait.

You've made a DNS change — updated your A record, switched nameservers, or added an MX record. But the change doesn't seem to be working yet. Why? This is DNS propagation, and it's completely normal. This guide explains what it is and what to expect.

Quick summary

DNS propagation is the time it takes for a DNS change to reach the DNS servers around the world. How long it takes depends on the record's TTL — the length of time other servers are told to keep their cached copy. For a nameserver change, registrars commonly tell you to allow 24 to 48 hours. You can't speed up a change once it's made, but you can check how far it has spread using online tools.

Why DNS changes aren't instant

DNS servers around the world don't pull updates in real time. Instead, they cache (store) DNS records for a set period of time — called the TTL (Time To Live), measured in seconds. Until the cached record expires, a DNS server will continue using the old value even if you've updated it.

For example, if your A record has a TTL of 3600 (one hour), DNS servers that have already looked up your domain will keep using the old IP address for up to one hour before checking for a new value.

Once the TTL expires, they fetch the updated record — and the change takes effect for that server.

How long does propagation take?

Change type	What controls the wait	Usual guidance
DNS record update (A, CNAME, MX, TXT)	The record's TTL — each DNS server keeps its cached copy until the TTL runs out	Minutes with a low TTL; up to the full TTL otherwise
Nameserver change	Your registrar updating the delegation, plus the nameserver TTL — commonly a day	Allow a day; registrars usually quote 24 to 48 hours

Providers give slightly different numbers. Cloudflare's setup guide says to allow up to 24 hours while your registrar updates your nameservers. Namecheap says a nameserver change may take 24 to 48 hours, and its article goes on to explain why it can stretch to 72. Either way, the TTL is the best guide you have: a DNS server can't see your change until its cached copy expires.

Nameserver changes take longer than record changes because they change the authoritative delegation for your whole domain, and the nameserver TTL is usually much higher than a record's.

Why some people see the change and others don't

Different DNS servers cache records for different periods. Your ISP's DNS server might have cached the old record. Your visitor's ISP might be checking fresh. This is why you might see the new site immediately while a colleague still sees the old one.

This inconsistency is normal and temporary. It resolves itself once all caches expire.

How to check propagation progress

You can check how far a DNS change has spread using free tools:

whatsmydns.net — Shows what DNS servers around the world are returning for your domain. Cloudflare's own setup guide points people here to confirm a nameserver change.
Dig (DNS lookup) — Google's hosted lookup tool. Enter your domain, pick a record type, and see the current answer.

In either tool you give your domain and the record type (A, MX, TXT, etc.) and see what DNS servers currently return. One caveat, straight from Cloudflare's docs: most of these tools cache results themselves, so they can lag slightly behind the real picture.

How to speed up propagation

You can't make propagation happen faster once a change is made, but you can reduce the TTL before making the change:

Lower the TTL of the record you're about to change to 300 seconds (5 minutes) — do this at least one full TTL cycle before you make the actual change. For example, if the current TTL is 3600 seconds (1 hour), lower it an hour before you plan to make the change.

Make the DNS change once the low TTL has had time to propagate.

After the change has propagated, restore the TTL to 3600 (1 hour) or 86400 (24 hours) for normal operation.

We often do this automatically before DNS migrations.

Flushing your local DNS cache

Sometimes your own computer has cached the old DNS record. You can flush your local DNS cache to force it to look up fresh records:

Open Command Prompt and run: ipconfig /flushdns

Microsoft describes this as flushing and resetting the contents of the DNS client resolver cache.

After flushing, try visiting your site in an incognito/private browser window to test with a fresh lookup.

Common questions

It's been 48 hours and the change still hasn't propagated. What should I do?

After 48 hours, if the change still isn't reflecting, there may be an error in the DNS record itself. Check that the record was saved correctly in your DNS management panel. If everything looks right, contact us — it could be a more unusual issue.

My site is offline during propagation. Is that normal?

Brief inconsistency is normal. But if your site is completely offline for more than a few hours, there may be an issue with the DNS record values themselves, not just propagation. Verify the record values are correct.

What is TTL and can I change it?

TTL (Time To Live) is the number of seconds a DNS record is cached by other servers. You can usually change it in your DNS management panel. Lower TTL = changes take effect sooner but more DNS queries. Higher TTL = faster lookups but changes take longer to go into effect. Some providers set the TTL for you on certain records — Cloudflare fixes proxied records at Auto, which is 300 seconds.

Does propagation affect my email?

Yes. If you change MX records or nameservers, email delivery can be disrupted during propagation. Plan email-related DNS changes carefully, especially if changing nameservers, and verify email is working after the change.

Need a hand?

If you're stuck, email support@chykalophia.com and we'll help. Include your website address and a screenshot if you can.