📡 Monitor your APIs — know when they go down before your users do
Better Stack checks uptime every 30 seconds with instant Slack, email & SMS alerts. Free tier available.
Affiliate link — we may earn a commission at no extra cost to you
DNS Propagation: How Long It Takes and How to Check It (2026)
You've updated your DNS records but your site still shows the old server. What's happening? DNS propagation is the process of your DNS changes spreading to resolvers worldwide — and it doesn't happen instantly. This guide explains how DNS propagation works, how long it actually takes, and how to track and speed it up.
⚡ Quick Summary
24–48h
Typical global propagation time
300s
Recommended pre-change TTL
~2h
Typical time to reach 95% of resolvers
What is DNS Propagation?
DNS propagation is the time it takes for a DNS record change to spread from your authoritative nameserver to DNS resolvers worldwide. When you update a DNS record (like pointing your domain to a new IP address), the change doesn't take effect everywhere instantly.
Here's why: DNS resolvers (the servers that translate domain names into IP addresses) cache DNS records for efficiency. When they look up a domain, they store the result locally for a set period — defined by the record's TTL (Time to Live) value. Until that cached record expires, the resolver serves the old data even if you've updated it.
How DNS Resolution Works
Because ISPs, corporate networks, and public resolvers all have different cache ages — and different users point to different resolvers — propagation is uneven. Some users see the new record in minutes; others may not see it for 48 hours.
How Long Does DNS Propagation Take?
The official answer is “up to 48 hours.” The real-world answer depends on your TTL:
| Your TTL Before Change | 50% Global Propagation | 95% Global Propagation |
|---|---|---|
| 300 sec (5 min) | ~10 minutes | ~30 minutes |
| 3,600 sec (1 hour) | ~1 hour | ~3 hours |
| 14,400 sec (4 hours) | ~4 hours | ~8 hours |
| 86,400 sec (24 hours) | ~12 hours | ~48 hours |
How to Check DNS Propagation
There are three ways to check whether your DNS change has propagated to a specific location:
1. Online DNS Propagation Checkers
The fastest way to check propagation globally. These tools query DNS resolvers in 20+ countries simultaneously and show you which locations see your new record.
2. Command Line (dig / nslookup)
Check what a specific DNS resolver sees right now. Useful for testing from your own machine:
dig @8.8.8.8 yourdomain.com ACheck A record via Google DNS
dig @1.1.1.1 yourdomain.com ACheck A record via Cloudflare DNS
nslookup yourdomain.com 8.8.8.8Windows-compatible alternative
dig +short yourdomain.comSee just the IP, no extra output
3. Check Your Local Cache
Your own computer caches DNS too. To see the freshest result, flush your local DNS cache:
macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderWindows:
ipconfig /flushdnsLinux:
sudo systemctl restart nscd (or resolved)Chrome:
chrome://net-internals/#dns → Clear host cacheMonitor DNS changes and uptime in one place
Better Stack monitors DNS health, SSL certificates, and uptime across 10+ global regions — alerting you the moment something breaks after a DNS change. Start free.
Try Better Stack Free →DNS Record Types and Propagation
Different DNS record types have different propagation characteristics and TTL defaults:
| Record Type | Purpose | Typical TTL |
|---|---|---|
| A | Maps domain to IPv4 address | 1 hour–24 hours |
| AAAA | Maps domain to IPv6 address | 1 hour–24 hours |
| CNAME | Alias to another domain name | 1 hour–24 hours |
| MX | Mail server routing | 1 hour–24 hours |
| TXT | SPF, DKIM, domain verification | 1 hour–24 hours |
| NS | Nameserver delegation | 24 hours–48 hours (slowest) |
| SOA | Zone authority information | 1 hour |
NS record changes are the slowest. When you change your nameservers (e.g., moving from GoDaddy to Cloudflare), propagation takes 24–48 hours because the parent zone (.com, .io, etc.) must update and propagate independently.
How to Speed Up DNS Propagation
You can't force other people's resolvers to flush their caches. But you can minimize propagation time with proper planning:
Lower TTL 24–48 hours before changes
HighChange your record's TTL to 300 seconds (5 minutes) one or two days before your planned DNS change. This ensures existing caches expire quickly before your change happens. After propagation confirms, raise TTL back to 3,600 or higher.
Use a fast DNS provider
MediumDNS providers like Cloudflare, NS1, and AWS Route 53 have massive global anycast networks. Changes propagate to their global PoPs near-instantly — often within seconds. Traditional registrar DNS (GoDaddy, Namecheap default DNS) can be slower.
Use Cloudflare Cache Purge
MediumIf your domain is behind Cloudflare, purge the DNS cache at 1.1.1.1/purge-cache. For Google DNS (8.8.8.8), use Google Admin Toolbox's Flush Cache tool. This clears those two public resolvers but won't affect ISP resolvers.
Test with a different resolver before going live
HighBefore cutting over, query your authoritative nameserver directly: dig @ns1.yourregistrar.com yourdomain.com A. If it shows the new record but 8.8.8.8 still shows the old one, propagation is just cache lag — not a configuration error.
Plan DNS changes during low-traffic windows
LowEven with short TTLs, there's a window where some users see the old record and some see the new one. Schedule changes during off-peak hours (2–4 AM local time) to minimize user impact during the propagation window.
Common DNS Propagation Problems
"My site is down for some users but not others"
Cause: Normal propagation. Some resolvers see new record; others have old one cached.
Fix: Wait for TTL to expire. Use a DNS propagation checker to see worldwide status.
"DNS is propagated but site still doesn't load"
Cause: DNS is resolved correctly but the server isn't configured for the domain, or SSL hasn't been provisioned.
Fix: Check web server config. If using HTTPS, verify SSL certificate includes the new domain/subdomain.
"Propagation is stuck — same old IP after 48 hours"
Cause: The change may not have saved correctly, or you're editing the wrong record type (CNAME vs A).
Fix: Query your authoritative nameserver directly (dig @ns1.yourregistrar.com yourdomain.com). If it shows the old record, the change didn't save.
"Email stopped working after DNS change"
Cause: MX records may have been overwritten during nameserver migration, or SPF/DKIM records weren't migrated.
Fix: Check MX records: dig yourdomain.com MX. Verify SPF and DKIM TXT records match your email provider's requirements.
"I see the new site but others don't"
Cause: Your local DNS cache or ISP resolver has refreshed, but others haven't.
Fix: Confirm using DNSChecker.org. Explain to affected users that their ISP resolver will update within 24-48 hours.
Alert Pro
14-day free trialStop checking — get alerted instantly
Next time your domains goes down, you'll know in under 60 seconds — not when your users start complaining.
- Email alerts for your domains + 9 more APIs
- $0 due today for trial
- Cancel anytime — $9/mo after trial
DNS Propagation Checklist
Use this checklist for any DNS migration or domain change:
Frequently Asked Questions
How long does DNS propagation take?
DNS propagation typically takes 24–48 hours for full global propagation. However, with a low TTL (300 seconds), most resolvers see your change within minutes to a few hours. The time is largely determined by the TTL you had set before making the change.
Does DNS propagation affect SSL/HTTPS?
Yes — SSL certificate issuance often requires DNS propagation first. If you're using Let's Encrypt or a CDN like Cloudflare for SSL, the certificate cannot be issued for your domain until DNS resolves correctly. Wait for full propagation before expecting HTTPS to work on a newly pointed domain.
Why does my DNS change show up on my phone but not my computer?
Your phone and computer likely use different DNS resolvers. Mobile carriers often use their own DNS servers with different cache lifetimes. Try flushing your computer's DNS cache (ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS) and then re-check.
Is 48-hour DNS propagation still normal in 2026?
48 hours is the maximum worst-case scenario with a high TTL. In practice, most DNS changes propagate to the majority of users within 4–8 hours with a default TTL of 3,600 seconds. With a pre-lowered TTL of 300 seconds, propagation completes within 30–60 minutes for most resolvers.
What's the fastest DNS provider for propagation?
Cloudflare DNS is widely considered the fastest for both propagation and resolution speed. NS1, AWS Route 53, and Google Cloud DNS are also fast options for production use. Cloudflare propagates changes to its 300+ global PoPs within seconds of saving.
🛠 Tools We Use & Recommend
Tested across our own infrastructure monitoring 200+ APIs daily
SEO & Site Performance Monitoring
Used by 10M+ marketers
Track your site health, uptime, search rankings, and competitor movements from one dashboard.
“We use SEMrush to track how our API status pages rank and catch site health issues early.”
Monitor Your Domain After DNS Changes
DNS changes can break uptime. Set up automatic monitoring to catch issues immediately after a migration — before users report them.