Troubleshooting DNS Propagation Issues

By Admin · Feb 25, 2026 · Updated Apr 25, 2026 · 67 views · 2 min read

What Is DNS Propagation?

When you change DNS records, the update does not take effect globally instantly. DNS servers around the world cache records according to their TTL (Time to Live). Propagation is the time it takes for all caches to expire and reflect the new records.

Check Current DNS State

# Check what different DNS servers see
dig example.com @1.1.1.1 +short     # Cloudflare
dig example.com @8.8.8.8 +short     # Google
dig example.com @9.9.9.9 +short     # Quad9
dig example.com @208.67.222.222 +short  # OpenDNS

Check TTL Values

dig example.com A | grep -A1 "ANSWER SECTION"
# The number before IN is the remaining TTL in seconds

Common Propagation Times

Change Type	Typical Time
A/AAAA record (low TTL)	5-30 minutes
A/AAAA record (high TTL)	1-24 hours
Nameserver change	24-48 hours
New domain	1-24 hours

Speed Up Propagation

Lower TTL before changes — set TTL to 300 (5 minutes) at least 24 hours before making changes
Make the change — update the record
Raise TTL after — once propagated, set TTL back to 3600+ for performance

Flush Local DNS Cache

# Linux
sudo systemd-resolve --flush-caches
# or
sudo resolvectl flush-caches

# macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Windows
ipconfig /flushdns

Common Issues

Stale cache — old TTL was very high (86400 = 24h). Just wait.
Wrong nameservers — domain registrar still pointing to old nameservers
Conflicting records — CNAME at root conflicting with other records
ISP caching — some ISPs ignore TTL and cache longer. Try a VPN to verify.