DNS Propagation Checker
Verify DNS changes have propagated worldwide. Check 50+ nameservers across continents in real-time.
What It Does
After changing DNS records (A, MX, CNAME, etc.), it takes time to propagate globally (5 min - 48 hours). This tool queries nameservers worldwide to show propagation status.
Quick Check
- Go to DNS Propagation Checker
- Enter domain + select record type (A, AAAA, MX, TXT, CNAME)
- Click "Check" — see results from 50+ locations
- Green = propagated | Red = old value | Yellow = partial
How DNS Propagation Works
- You update DNS: Change A record from 1.2.3.4 to 5.6.7.8
- Authoritative NS updated: Your DNS provider (Cloudflare, Route53) sees new value immediately
- TTL countdown: Cached records expire after TTL seconds
- Resolvers refresh: Public resolvers (Google 8.8.8.8, Cloudflare 1.1.1.1) query authoritative NS for new value
- Full propagation: All resolvers worldwide have new value
Propagation Time Factors
- TTL (Time To Live): Records cached for this many seconds. Lower TTL = faster propagation.
- Resolver behavior: Some ignore TTL, cache longer (ISPs do this to save bandwidth)
- Geographic distance: Servers farther from authoritative NS may be slower
- Record type: NS record changes take longest (can be 48 hours)
Tested Locations
Tool queries nameservers in:
- North America (10 locations: US East, US West, Canada)
- Europe (15 locations: UK, Germany, France, Netherlands, etc.)
- Asia (12 locations: Tokyo, Singapore, Hong Kong, India)
- South America (3 locations: Brazil, Argentina)
- Africa/Middle East (5 locations)
- Oceania (3 locations: Australia, New Zealand)
Common Scenarios
1. Migrating to New Server
Steps:
- Lower TTL to 300 (5 minutes) 24 hours before migration
- Change A record to new server IP
- Use propagation checke to verify
- Once 100% propagated, raise TTL back to 3600
2. Switching DNS Providers
Challenge: NS record changes take longest (24-48 hours)
Solution:
- Set up DNS records on new provider (exact copy of old)
- Update NS records at domain registrar
- Monitor with propagation checker
- Keep old DNS active for 72 hours (safety buffer)
3. Email Migration (MX Records)
Critical: Email can be lost if MX records point to wrong server during migration.
Safe Approach:
- Keep both old and new MX records active (different priorities)
- Monitor propagation (ensure all resolvers see new MX)
- After 100% propagation + 24 hours, remove old MX
Interpreting Results
| Status | Meaning | Action |
|---|---|---|
| Green (100%) | All resolvers show new value | ✅ Propagation complete! |
| Yellow (50-99%) | Most resolvers updated, some still showing old | ⏳ Wait 1-2 more hours |
| Red (< 50%) | Most showing old value | 🔍 Check authoritative NS — is update saved? |
| Gray | No response / NXDOMAIN | ❌ Record doesn't exist or typo in domain name |
Troubleshooting
Propagation Stuck at 80%?
Cause: Some ISP resolvers ignore TTL, cache aggressively.
Solution: Wait 24-48 hours. ISPs eventually refresh. Can't be forced.
New Record Not Appearing Anywhere?
- Check authoritative nameserver directly:
dig @ns1.yourdnsprovider.com yourdomain.com A - If no response from authoritative NS → DNS provider issue (contact support)
- If authoritative NS shows new value but propagation checker doesn't → Wait for cache expiry
Different Values in Different Regions?
Possible if using geo-DNS (e.g., Route53 geolocation routing). Tool will show different IPs based on resolver location — this is intentional!
Best Practices
- ✅ Lower TTL 24 hours before making changes
- ✅ Make DNS changes during low-traffic hours
- ✅ Keep old services running for 24 hours after propagation
- ✅ Test from multiple devices/networks before declaring success
- ❌ Don't assume instant propagation (even with 60s TTL, some cache longer)
- ❌ Don't delete old DNS records immediately after update
- ❌ Don't change NS records without 48-hour buffer plan