You updated your domain.
You cleared cache.
You refreshed 20 times.
Still seeing the old website?
Welcome to DNS propagation.
🌍 What’s Actually Happening?
When you change a DNS record (A, MX, TXT, NS, etc.), the update doesn’t go live worldwide instantly.
Why?
Because DNS data is cached by:
ISPs
Public DNS resolvers (Google, Cloudflare)
Browsers
Operating systems
This caching improves performance — but it also causes delay after changes.
⏳ How Long Does DNS Propagation Take?
It depends on TTL (Time To Live).
Example:
TTL = 3600 seconds (1 hour)
That means some users may still see old data for up to 1 hour.
In some cases, propagation can take:
5–30 minutes
Up to 24–48 hours (rare but possible)
🔎 How I Check If DNS Has Updated Globally
Instead of guessing, I check DNS status from multiple regions.
I use this DNS lookup tool:
It lets you instantly check:
A Records
MX Records
TXT Records
CNAME
NS Records
This helps quickly confirm whether the issue is propagation or something else.
🧠 Pro Tip for Developers
Before migrating servers:
✔ Lower TTL 24 hours in advance
✔ Wait for TTL to expire
✔ Then update DNS
This reduces downtime significantly.
Top comments (0)