ProbeOps
HomeToolsPricingDownloadsAboutContact Us
Login/Sign Up

DNS Propagation Troubleshooting

Quick Answer

DNS propagation typically takes 24-48 hours but can be faster depending on TTL settings. To check if DNS has propagated: use ProbeOps DNS Lookup at probeops.com/tools/dns-lookup to query records from 6 global locations simultaneously. If results differ between regions, propagation is still in progress. To speed up propagation, lower your TTL to 300 seconds before making changes.

When to Troubleshoot DNS Propagation

  • After changing nameservers or DNS provider
  • When updating A, AAAA, or CNAME records for a domain
  • After modifying MX records for email routing
  • When website shows old content after server migration
  • When some users can access site but others cannot

Step-by-Step Troubleshooting Guide

Step 1: Check Current DNS Records

Use ProbeOps DNS Lookup to query your domain's current records. Enter your domain and select the record type (A, AAAA, CNAME, MX, TXT, NS). Compare the returned values with what you configured in your DNS provider.

Step 2: Compare Across Regions

Run DNS lookups from multiple geographic locations. If US servers return one IP but European servers return another, propagation is incomplete. Wait and recheck, or investigate why specific regions have stale data.

Step 3: Check TTL Values

TTL (Time-To-Live) determines how long DNS resolvers cache records. A TTL of 3600 means records are cached for 1 hour. If you recently changed records, wait at least one full TTL period for global propagation.

Step 4: Flush Local DNS Cache

Your computer and browser cache DNS records. Clear these caches to see updated records: Windows: ipconfig /flushdns, macOS: sudo dscacheutil -flushcache, Chrome: chrome://net-internals/#dns

Step 5: Verify Authoritative Nameservers

Query the authoritative nameservers directly to confirm they have correct records. Use NS record lookup to find authoritative servers, then query them specifically.

Example: Checking DNS Propagation

Input

Domain: example.com, Record Type: A

Output

US East: 93.184.216.34 (TTL: 3600), US West: 93.184.216.34 (TTL: 3600), EU Central: 93.184.216.34 (TTL: 3600), AP South: 93.184.216.34 (TTL: 3600). Status: Fully propagated - all regions return same IP.

Common DNS Propagation Problems

Problem: DNS changes not appearing after 48 hours

Fix: Verify changes were saved at your DNS provider. Check you're editing the correct zone file. Ensure nameservers are correctly delegated at your registrar.

Problem: Some users see old site, others see new site

Fix: This is normal during propagation. Different ISPs cache records for different durations. Wait for full TTL expiration across all networks.

Problem: DNS works on mobile but not desktop

Fix: Desktop has cached old DNS. Flush DNS cache on the device and restart browser. Mobile networks often have shorter cache times.

Related Tools

Guides/DNS Propagation Troubleshooting

DNS Propagation Troubleshooting

Learn how to check if DNS changes have propagated globally and troubleshoot common DNS issues that prevent your domain from resolving correctly.

Quick Answer

DNS propagation typically takes 24-48 hours depending on TTL settings. To check propagation status, use a multi-region DNS lookup tool to query records from different locations. If all regions return the same value, propagation is complete. To speed up future changes, lower your TTL to 300-600 seconds before making modifications.

When to Use This

  • After changing nameservers or switching DNS providers
  • When updating A, AAAA, or CNAME records for your domain
  • After modifying MX records for email routing changes
  • When your website shows old content after server migration
  • When some users can access your site but others cannot

Step-by-Step Guide

1

Check Current DNS Records

Use the ProbeOps DNS Lookup tool to query your domain. Select the record type (A, AAAA, CNAME, MX, TXT, NS) and compare returned values with your DNS provider settings.

2

Compare Across Regions

Run lookups from all 6 global locations. If results differ between regions, propagation is still in progress. Consistent results across all regions means propagation is complete.

3

Check TTL Values

Note the TTL (Time-To-Live) in results. This tells you how long records are cached. Wait at least one full TTL period after changes for global propagation.

TTL: 3600 = 1 hour cache, TTL: 86400 = 24 hour cache
4

Flush Local DNS Cache

Clear your local DNS cache to see updated records immediately on your machine.

Windows: ipconfig /flushdns macOS: sudo dscacheutil -flushcache Linux: sudo systemd-resolve --flush-caches

Example: Checking A Record Propagation

Input

example.com (A record)

Output

US East (Virginia): 93.184.216.34 TTL: 3600 US West (Oregon): 93.184.216.34 TTL: 3600 EU Central (Helsinki): 93.184.216.34 TTL: 3600 AP South (Mumbai): 93.184.216.34 TTL: 3600 CA Central (Canada): 93.184.216.34 TTL: 3600 AP Southeast (Sydney): 93.184.216.34 TTL: 3600 Status: ✓ Fully propagated - all regions consistent

Common Pitfalls & Quick Fixes

Problem: DNS changes not appearing after 48+ hours

Fix: Verify changes were actually saved at your DNS provider. Check you're editing the correct zone file. Ensure nameservers are properly delegated at your domain registrar.

Problem: Some users see old site, others see new site

Fix: This is normal during propagation. Different ISPs cache records for varying durations based on TTL. Wait for full propagation or ask affected users to flush their DNS cache.

Problem: Changed nameservers but DNS still points to old provider

Fix: Nameserver changes at registrar level can take 24-48 hours. Verify the NS records are updated at the registrar (not just DNS provider). Check WHOIS for current nameservers.

Try it yourself

Use our free DNS Lookup to run these checks from 6 global locations.

Open DNS Lookup
View API Docs

Related Guides

Check SSL Certificate Expiry

DNS Propagation Troubleshooting

How to Read Traceroute Results

Check if Ports are Open