DNS Propagation: Why Your Changes Aren't Showing
(And How to Fix It)
Published May 1, 2026 · 5 min read
You updated your DNS records. It's been 3 hours. Nothing changed. Are you doing something wrong? No. This is DNS propagation — and here's exactly how long it takes and how to check it.
What Is DNS Propagation?
When you change a DNS record — like pointing your domain to a new server or adding an SPF record — that change doesn't instantly reach every corner of the internet. Instead, it propagates through a hierarchy of DNS servers worldwide.
Think of it like dropping a stone in a pond. The ripple starts at your DNS provider, spreads to your ISP's resolvers, then to regional resolvers, and eventually to every DNS server that has your domain cached. Each server updates at its own pace.
How Long Does DNS Propagation Take?
15 min
Google DNS (8.8.8.8)
Cloudflare (1.1.1.1)
1-4 hrs
ISPs (Comcast, AT&T)
Corporate DNS
24-48 hrs
Worst case
High TTL records
The single most important factor: your TTL (Time To Live) value. If your old record had TTL=86400 (24 hours), every DNS resolver that cached it will hold onto the old value for up to 24 hours before checking for updates.
The #1 DNS Propagation Mistake
People run nslookup or dig from their local machine, see the new record, and think "great, it propagated." Then a customer in Tokyo reports the site is still down.
Your local DNS resolver might update in 5 minutes. A resolver in Singapore might take 12 hours. You need to check from multiple locations worldwide.
How to Check DNS Propagation (Free, No Signup)
- Go to Korpo.Pro DNS Propagation Checker
- Type your domain (e.g.,
example.com) - Select the record type you changed (A, MX, TXT, CNAME, etc.)
- Click "Check Propagation"
- See results from 15+ global DNS resolvers — instantly
What Each Result Means
| You See | It Means |
|---|---|
| ✅ New IP everywhere | Propagation complete. Done. |
| ⚠️ Mixed results | Wait longer. Check TTL. Try again in 1 hour. |
| ❌ Old IP everywhere | TTL may be very high. Or your change didn't save. Double-check at your registrar. |
| ❌ No records at all | Record was deleted or never existed. Re-add it. |
3 Tricks to Speed Up DNS Propagation
- Lower TTL before changes. Set TTL=300 (5 min) 24 hours before making any DNS change. Old resolvers expire their cache faster.
- Flush your own DNS cache. On Mac:
sudo dscacheutil -flushcache. On Windows:ipconfig /flushdns. On Linux:sudo systemd-resolve --flush-caches. - Use public DNS temporarily. Switch to Google DNS (8.8.8.8) or Cloudflare (1.1.1.1) — they update faster than ISP resolvers.
When Propagation Problems Aren't Really Propagation
Sometimes DNS changes don't show up because of non-propagation issues:
- Typo in the record value. One wrong character and the record resolves to nothing.
- Forgot to save. Many registrars require clicking "Save" or "Apply Changes" after editing.
- DNSSEC issues. If DNSSEC is enabled and you change nameservers, you need to update DS records at your registrar.
- CNAME at apex. You can't put a CNAME on the root domain (example.com). Use A records or ALIAS/ANAME.
📊 Also: Get Your Full Email Health Report
While you wait for DNS to propagate, check your email deliverability. Many DNS changes (SPF, DKIM, DMARC) directly affect whether your emails reach inboxes.
📄 Email Health Report — €9 →TL;DR
- DNS propagation takes 15 minutes to 48 hours depending on TTL and location.
- Check from multiple global locations — not just your machine.
- Lower TTL before making changes to speed things up.
- Use the free DNS propagation checker at Korpo.Pro to see results from 15+ resolvers worldwide.