DNS Propagation Checker
DNS & Networking
Monitor DNS propagation globally and verify DNS changes across multiple locations worldwide. Track nameserver updates in real-time.
On This Page
What is DNS Propagation?
DNS propagation is the time it takes for DNS changes (like updating your domain's IP address or nameservers) to spread across the entire internet. When you change DNS records, it doesn't update instantly worldwide.
The internet has thousands of DNS servers that cache records to improve performance. Each cache has a Time To Live (TTL) value that determines how long it stores records before checking for updates. This caching mechanism causes propagation delays.
How DNS Works
- 1. User types domain name in browser
- 2. Browser queries local DNS resolver
- 3. If cached, returns immediately; if not, queries upstream
- 4. Query goes through recursive DNS servers to authoritative servers
- 5. Authoritative server returns the correct IP address
- 6. Result is cached at multiple levels with TTL
Why Check DNS Propagation?
Verify Domain Changes
After updating DNS records, check if changes have propagated to ensure your domain points to the right server globally.
Migration Planning
When migrating to a new server or hosting provider, monitor propagation to know when it's safe to decommission the old server.
Troubleshooting DNS Issues
Diagnose why some users see your old site while others see the new one. Identify regions where DNS hasn't updated yet.
Email Configuration
Verify MX record changes have propagated to ensure email delivery isn't disrupted after DNS updates.
How to Use the DNS Propagation Checker
Enter Your Domain
Type your domain name without http:// or https://
Example: example.com
Select Record Type
Choose the DNS record type you want to check:
- • A Record: IPv4 address
- • AAAA Record: IPv6 address
- • CNAME: Canonical name (alias)
- • MX: Mail exchange servers
- • TXT: Text records (SPF, DKIM, etc.)
- • NS: Nameserver records
View Global Results
The tool queries DNS servers from multiple locations worldwide:
- ✓ North America (USA, Canada)
- ✓ Europe (UK, Germany, France)
- ✓ Asia (Japan, Singapore, India)
- ✓ Australia & Oceania
- ✓ South America (Brazil)
Analyze Results
Check for consistency:
- ✅ All green: Fully propagated worldwide
- 🟡 Mixed results: Still propagating
- 🔴 All old values: Changes not detected yet
DNS Record Types Explained
A Record (Address)
Maps domain names to IPv4 addresses. Most common record type.
Example: example.com → 192.168.1.1
AAAA Record
Maps domain names to IPv6 addresses.
Example: example.com → 2001:0db8:85a3::8a2e:0370:7334
CNAME Record (Canonical Name)
Creates an alias pointing to another domain.
Example: www.example.com → example.com
MX Record (Mail Exchange)
Directs email to mail servers. Includes priority values.
Example: 10 mail.example.com
TXT Record
Stores text information. Used for SPF, DKIM, domain verification.
Example: v=spf1 include:_spf.example.com ~all
NS Record (Nameserver)
Specifies authoritative nameservers for the domain.
Example: ns1.example.com, ns2.example.com
Understanding Propagation Timeframes
Typical Propagation Times
Factors Affecting Propagation Speed
- • TTL (Time To Live): Lower TTL = faster propagation
- • ISP DNS Caching: Some ISPs cache longer than TTL
- • Record Type: Nameserver changes take longer
- • Geographic Location: Remote regions may update slower
- • DNS Provider: Different providers have different update speeds
Troubleshooting DNS Issues
Changes Not Propagating
Cause: High TTL, DNS cache, or incorrect configuration
Solution: Wait for TTL to expire, flush local DNS cache, verify changes in DNS panel
Inconsistent Results Globally
Cause: Normal during propagation or GSLB/GeoDNS setup
Solution: Wait if propagating; verify GeoDNS rules if intentional
Old Records Still Showing
Cause: Local cache or long TTL from previous record
Solution: Flush DNS cache: ipconfig /flushdns (Windows) or sudo killall -HUP mDNSResponder (Mac)
NXDOMAIN Error
Cause: Domain doesn't exist or nameservers misconfigured
Solution: Verify domain registration, check nameserver configuration at registrar
Best Practices
Lower TTL Before Changes
24-48 hours before making DNS changes, lower TTL to 300 seconds (5 minutes) to speed up propagation.
Test During Low Traffic
Make DNS changes during off-peak hours to minimize impact if issues occur.
Keep Old Server Running
Don't shut down old servers until DNS has fully propagated globally (wait 72 hours after verification).
Monitor Continuously
Use our DNS checker to monitor propagation every few hours until all locations show updated records.