DNS Propagation Checker

Enter a domain name to query its DNS records across multiple record types using Google Public DNS. View A, AAAA, MX, CNAME, TXT, NS, and SOA records with TTL values to understand propagation status. All queries run directly from your browser.

Enter Domain Name

What Is DNS Propagation?

DNS propagation is the process by which updated DNS records spread across the global network of DNS servers. When you change a DNS record — such as updating your domain's A record to point to a new server or modifying MX records for email — it takes time for every DNS resolver worldwide to receive the update. This delay is DNS propagation.

The propagation time depends primarily on the TTL (Time to Live) value set on your records. If your A record has a TTL of 3600 seconds (1 hour), DNS resolvers will cache the old value for up to one hour before fetching the new one. Understanding this process is crucial when changing DNS settings on your router or migrating to a new hosting provider. You can check your current DNS configuration with our DNS Lookup tool.

DNS Record Types Explained

This tool queries multiple DNS record types. Each serves a different purpose in the Domain Name System:

Record Type	Purpose	Example Value	Common TTL
A	Maps domain to IPv4 address	93.184.216.34	300-3600s
AAAA	Maps domain to IPv6 address	2606:2800:220:1::248	300-3600s
MX	Mail server for the domain	10 mail.example.com	3600-86400s
CNAME	Alias to another domain name	www.example.com → example.com	300-3600s
TXT	Verification, SPF, DKIM, DMARC	v=spf1 include:_spf.google.com ~all	300-3600s
NS	Authoritative name servers	ns1.example.com	86400s
SOA	Zone authority and serial number	ns1.example.com admin.example.com	86400s

Pro Tip: Before making DNS changes, lower the TTL to 300 seconds (5 minutes) at least 24 hours in advance. This ensures the old long TTL expires and resolvers start checking more frequently. After the change is confirmed and propagated, raise the TTL back to a higher value like 3600 or 86400 to reduce query load. Use this tool to verify the TTL values on your current records before making changes.

How Long Does DNS Propagation Take?

Propagation time varies based on several factors. Here's a practical guide to expected timelines when making DNS changes:

Change Type	Typical Propagation	Maximum Wait	Notes
A / AAAA record update	5 min - 4 hours	48 hours	Depends on previous TTL value
MX record change	1 - 12 hours	72 hours	MX records often have higher TTLs
Nameserver change	12 - 48 hours	72 hours	Involves registry-level updates
TXT record (SPF/DKIM)	5 min - 4 hours	48 hours	Critical for email authentication
New domain registration	1 - 24 hours	48 hours	TLD nameservers must update

If your DNS changes don't seem to be propagating, your local resolver might be caching old results. Try flushing your DNS cache or using a different DNS server. You can also check if the issue is specific to your network by comparing results from your local connection versus an external tool.

Understanding TTL Values

TTL (Time to Live) is the most important factor controlling DNS propagation speed. It tells DNS resolvers how long to cache a record before querying the authoritative server again. When you manage your home network through 192.168.1.1 or 10.0.0.1, your router's DNS cache also respects TTL values.

# Check TTL of a specific record using dig
dig example.com A +noall +answer

# Output shows TTL in seconds:
# example.com.    300    IN    A    93.184.216.34
#                 ^^^
#              TTL = 300 seconds (5 minutes)

# Flush DNS cache on Windows
ipconfig /flushdns

# Flush DNS cache on macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

# Flush DNS cache on Linux (systemd-resolved)
sudo systemd-resolve --flush-caches

Note: Even after the TTL expires, some ISP resolvers may cache records longer than specified. This is called "sticky DNS" and is relatively uncommon but can explain why propagation seems slow for some users. If you're experiencing this, try switching to a public DNS resolver like Google DNS (8.8.8.8) or Cloudflare (1.1.1.1). See our guide on how to change DNS on your router.

Troubleshooting DNS Propagation Issues

When DNS changes don't appear to propagate, follow this systematic approach:

Verify the change at the authoritative server — Query your domain's authoritative nameserver directly to confirm the change was applied. Use our DNS Lookup tool to find your NS records first.
Check the TTL of the old record — If the old record had a TTL of 86400 (24 hours), you may need to wait that long for all caches to expire.
Flush your local DNS cache — Your computer and router both cache DNS results. Clear both caches when testing.
Test from multiple locations — Use this tool to query from Google DNS, which represents a global perspective.
Check for conflicting records — A CNAME record cannot coexist with other record types at the same name.

If your DNS server is not responding, the problem may be with your resolver configuration rather than propagation. Check your gateway settings and verify your network connectivity with a ping test.

DNS Propagation for Common Scenarios

Different migration scenarios require different DNS strategies. Here's how to minimize downtime for each:

Moving to a new web host — Set up the new server first, verify it works via direct IP, then update the A record. Use a low TTL beforehand.
Switching email providers — Configure the new provider completely, update MX and TXT (SPF/DKIM) records simultaneously to avoid authentication failures.
CDN setup — Most CDNs use CNAME records. Point your subdomain (www) to the CDN's edge, and use an A record for the apex domain.
SSL certificate issuance — Let's Encrypt and other CAs need to verify DNS during issuance. Ensure your records have propagated before requesting a certificate.

For IP-related changes, use our IP Lookup tool to verify the new server's IP details, and the Subnet Calculator to ensure your network configuration is correct. If you need to check whether DNS is resolving to an IP in the expected network class, use our class identifier tool.

Key Takeaways

DNS propagation is the time it takes for DNS changes to spread across all resolvers worldwide.
TTL is the primary factor — lower it before making changes, raise it after propagation confirms.
Most DNS changes propagate within 5 minutes to 4 hours; nameserver changes can take 24-48 hours.
Always verify changes at the authoritative nameserver first to confirm they were applied.
Flush your local DNS cache and router cache when testing propagation.
Use this tool alongside our DNS Lookup to verify both propagation status and record accuracy.

Video: DNS Propagation Explained

Related Guides

Frequently Asked Questions

How long does DNS propagation usually take?

Most DNS changes propagate within 5 minutes to 4 hours when TTL values are reasonable (300-3600 seconds). Nameserver changes take longer, typically 12-48 hours, because they involve registry-level updates. The maximum theoretical wait is 72 hours, but this is rare with modern DNS infrastructure.

Why do some users see the new site while others see the old one?

Different DNS resolvers cache records independently. When you update a DNS record, resolvers with expired caches will fetch the new value while others still serve the cached old value. This creates a period where different users see different results depending on which resolver they use.

Can I speed up DNS propagation?

You cannot force all DNS resolvers to update simultaneously. However, you can minimize propagation time by lowering the TTL well before making changes. Set it to 300 seconds (5 minutes) at least 24 hours ahead of your planned change. This ensures most resolvers will check back within 5 minutes.

Does changing nameservers affect email delivery?

Yes, changing nameservers can temporarily disrupt email delivery if MX records differ between the old and new nameservers. Ensure your new nameserver has identical MX, SPF, and DKIM records configured before switching. Monitor email with our DNS Lookup tool during the transition.

What does the TTL value mean in DNS records?

TTL (Time to Live) tells DNS resolvers how many seconds to cache a record before re-querying the authoritative server. A TTL of 3600 means the record is cached for 1 hour. Lower TTLs mean faster propagation but more DNS queries (higher load on your nameserver).

Why is my DNS change not showing even after 48 hours?

Check that the change was actually applied at your authoritative nameserver. Common issues include: changes saved but not published, conflicting records (CNAME with A record), domain registrar overriding nameserver settings, or your local DNS cache not being flushed. Try querying with dig @your-ns-server example.com directly.

Should I use Google DNS or Cloudflare DNS for testing?

Both are excellent for testing propagation. Google DNS (8.8.8.8) and Cloudflare DNS (1.1.1.1) have global anycast networks and typically refresh caches promptly. This tool uses Google DNS for queries. For your regular router DNS configuration, either provider works well.

About Tommy N.

Tommy is the founder of RouterHax and a network engineer with 10+ years of experience in home and enterprise networking. He specializes in router configuration, WiFi optimization, and network security. When not writing guides, he's testing the latest mesh WiFi systems and helping readers troubleshoot their home networks.