DNS Not Propagating Fix DNS Setup Guide

Why Is My DNS Not Propagating? Complete Troubleshooting Guide

DNS propagation delays are one of the most common frustrations when managing domains. After making DNS changes, you expect them to take effect immediately — but DNS doesn't work that way. This guide explains why DNS changes appear stuck, how TTL and caching affect propagation, and step-by-step fixes to speed things up.

Step-by-Step Setup Guide

1. Understand DNS TTL and Caching TTL (Time To Live) controls how long DNS records are cached by resolvers worldwide.
   • Every DNS record has a TTL value in seconds (e.g., 3600 = 1 hour)
   • Resolvers cache records for the TTL duration before re-querying
   • If your old TTL was 86400 (24 hours), resolvers may serve stale data for up to 24 hours
   • Lower your TTL to 300 (5 minutes) before making changes, then wait for old TTL to expire
2. Flush Your Local DNS Cache Your computer and browser cache DNS responses independently of ISP resolvers.
   • Windows: Run 'ipconfig /flushdns' in Command Prompt as Administrator
   • macOS: Run 'sudo dscacheutil -flushcache && sudo killall -HUP mDNSResponder' in Terminal
   • Linux: Run 'sudo systemd-resolve --flush-caches' or restart systemd-resolved
   • Also clear your browser cache or test in incognito/private browsing mode
3. Test with Multiple Public DNS Resolvers Compare results across different DNS providers to confirm propagation status.
   • Test with Google DNS (8.8.8.8) using 'nslookup yourdomain.com 8.8.8.8'
   • Test with Cloudflare DNS (1.1.1.1) using 'nslookup yourdomain.com 1.1.1.1'
   • Test with Quad9 (9.9.9.9) and OpenDNS (208.67.222.222)
   • Use ReviewMyDNS to check propagation across 50+ global servers simultaneously
4. Verify Changes at Authoritative Nameservers Check that your DNS provider's authoritative servers have the correct records.
   • Find your authoritative nameservers with 'dig NS yourdomain.com'
   • Query authoritative server directly: 'dig @ns1.yourdns.com yourdomain.com A'
   • If authoritative servers show old data, the change wasn't saved correctly
   • Re-check your DNS provider dashboard and save changes again
5. Check for ISP DNS Caching Issues Some ISPs aggressively cache DNS records beyond TTL values.
   • ISP resolvers sometimes ignore TTL and cache for longer periods
   • Switch to a public DNS resolver (Google 8.8.8.8 or Cloudflare 1.1.1.1) to bypass ISP caching
   • Contact your ISP if their DNS servers consistently show stale data
   • Corporate networks and VPNs may have their own DNS caching layers

Common DNS Record Types on DNS Propagation Issues

• A Record Propagation: A record changes are affected by the previous TTL value. If the old TTL was high, resolvers keep serving old IP. Lower TTL before migration. Old: A @ 192.0.2.1 TTL 86400 → New: A @ 203.0.113.1 TTL 300
• CNAME Record Propagation: CNAME changes follow the same TTL caching rules. Additionally, the target domain's own DNS resolution adds another layer of potential caching. Old: CNAME www old-host.com TTL 3600 → New: CNAME www new-host.com TTL 300
• MX Record Propagation: MX record changes affect email delivery. Keep old mail server active during propagation to avoid lost emails. MX changes can take 2-6 hours. Old: MX @ mail.old-provider.com TTL 3600 → New: MX @ mail.new-provider.com TTL 300
• NS Record Propagation: Nameserver changes are the slowest to propagate (24-48 hours). The registrar updates the parent zone, which must propagate through the global DNS hierarchy. Old NS: ns1.old-dns.com → New NS: ns1.new-dns.com

Troubleshooting Common Issues

• DNS shows old records after 24+ hours: Verify changes saved correctly at your DNS provider. Query authoritative nameservers directly to confirm. If authoritative servers show correct data but resolvers don't, aggressive ISP caching is likely — switch to public DNS (8.8.8.8 or 1.1.1.1) and wait.
• DNS works on some devices but not others: Different devices use different DNS resolvers with different cache states. Flush DNS cache on affected devices. Check if devices use ISP DNS vs public DNS. Corporate networks may have separate DNS infrastructure with longer cache times.
• Changed nameservers but domain not resolving: Nameserver changes take 24-48 hours. Ensure new nameservers are correct and active. Verify DNS records exist at the new DNS provider before changing nameservers. Query new nameservers directly to confirm records are configured.
• DNS propagation checker shows mixed results: Mixed results are normal during propagation — different servers update at different times. If most servers show new data, propagation is nearly complete. Wait for remaining servers. If stuck after 48 hours, check for DNSSEC issues or incorrect nameserver configuration.

Frequently Asked Questions

• How long does DNS propagation actually take? DNS propagation typically takes 15 minutes to 4 hours for record changes, and 24-48 hours for nameserver changes. The actual time depends on the previous TTL value, ISP caching behavior, and the type of change. Use ReviewMyDNS to monitor real-time propagation status across global servers.
• Can I speed up DNS propagation? You can't force all resolvers to update, but you can prepare: lower your TTL to 300 seconds 24-48 hours before making changes, flush your local DNS cache after changes, and use public DNS resolvers (8.8.8.8, 1.1.1.1) which typically update faster than ISP resolvers.
• Why does my DNS work on my phone but not my computer? Different devices use different DNS resolvers. Your phone may use mobile carrier DNS while your computer uses ISP or router DNS. Each resolver has its own cache. Flush DNS cache on the affected device, or switch to a public DNS resolver like Google (8.8.8.8) or Cloudflare (1.1.1.1).
• Does changing DNS affect my website's SEO? DNS changes themselves don't affect SEO, but downtime during propagation can. To minimize impact: lower TTL before changes, keep old server running during propagation, verify changes with ReviewMyDNS before decommissioning old infrastructure, and monitor for 404 errors after migration.