DNS Propagation Checker
DNS Propagation Checker
Compare results, latency, and error status across multiple recursive DNS and DoH providers. Great for diagnosing propagation delays and resolution forks.
After modifying DNS records, domain migration, or switching DNS servers, it usually takes minutes to 48 hours for records to propagate globally (propagation) due to TTL caching at each level of recursive resolvers. During this period, users in different regions may resolve to different results. This tool queries multiple global public DNS resolvers in real-time, supports traditional DNS, DoH, DoT protocols, simultaneously checks multi-type records (A/AAAA/CNAME/MX/NS/TXT etc.) and TTL remaining time, helping you quickly determine whether DNS changes have taken effect globally.
Related
Use Cases
- After modifying website A records or switching servers, use multi-node checks to confirm whether global resolvers have updated to new IP addresses, avoiding partial user access failures
- After configuring mailbox MX/SPF/DKIM records, verify whether TXT and MX records propagate globally to ensure mail delivery is normal
- After enabling DoH/DoT encrypted DNS, use protocol switching to verify whether DNS over HTTPS and DNS over TLS resolution results are correct
- When SSL certificate issuance fails (DV certificate requires DNS verification), use this tool to confirm whether _acme-challenge CNAME or TXT records have propagated globally
- When CDN switching or domain migration causes access anomalies, compare resolution results from different resolvers to determine if it's a DNS cache problem or origin issue
How to Use
- Enter the domain name to query in the input box (e.g. example.com), or click preset domain buttons (google.com/cloudflare.com etc.) for quick input
- Select record type: default is A record; can switch to AAAA/CNAME/MX/NS/TXT/SOA/CAA/PTR
- Select DNS resolvers: check multiple global public resolvers for simultaneous query, or use built-in resolver presets for quick selection
- Select resolution protocol: default is traditional DNS (53 port), can switch to DoH (DNS over HTTPS) or DoT (DNS over TLS)
- Click "Check DNS Propagation" button to see resolution results, IP addresses, TTL values and status from each node
- Use "Copy Results" button to copy diagnostic summary to clipboard
Features
- Multi-record type support: Query A, AAAA, CNAME, MX, NS, TXT, SOA, CAA, PTR nine record types, covering common DNS resolution scenarios
- Global multi-node check: Built-in multiple global public DNS resolvers (Google/Cloudflare/Quad9/OpenDNS/114DNS/Alidns/Tencent DNS) across different regions
- Multiple resolution protocols: Support traditional DNS (53/UDP), DNS over HTTPS (DoH), DNS over TLS (DoT) three protocol checks
- Common domain presets: Built-in quick presets for google.com, cloudflare.com, github.com, example.com, one-click verification
- Resolver presets: Built-in Google 8.8.8.8, Cloudflare 1.1.1.1, Quad9 9.9.9.9, OpenDNS, 114DNS, Ali DNS, Tencent DNS and other common resolvers
- One-click results copy: One-click copy DNS diagnostic results for pasting into operation records, ticket systems or technical reports
FAQ
How long does DNS propagation usually take?
<p>Depends on TTL settings and cache levels at each recursive resolver. Typically 5 minutes to 48 hours. After changing records, resolvers that have already cached the old record will wait for TTL expiry before fetching new records. Setting TTL lower (e.g. 300 seconds) 24 hours before migration can speed up propagation.</p>
Why do different DNS resolvers return different results?
<p>During propagation, some resolvers have cached old records while others have fetched new ones. Additionally, different resolvers are deployed in different regions, using different authoritative NS nodes, and may be affected by EDNS Client Subnet (ECS) or geographic DNS policies, leading to different resolution results. This is normal; waiting for TTL expiry will achieve consistency.</p>
What's the difference between DoH and traditional DNS?
<p>Traditional DNS uses UDP port 53 for plaintext transmission; ISPs or network operators can see or even tamper with DNS queries. DoH (DNS over HTTPS) encapsulates DNS in HTTPS traffic (port 443), same as normal web browsing traffic, effectively preventing DNS hijacking and surveillance. DoT uses TLS encryption on port 853 with similar security but different port.</p>
Why do NS records take so long to propagate?
<p>NS records are usually cached by top-level domain servers and recursive resolvers with longer default TTLs (often 48 hours or more). After changing NS servers, global full propagation usually takes 24–48 hours; this is normal. During this period, some users use new NS while others still use old NS. Ensure both old and new DNS servers have consistent records during the period.</p>
Does this tool query from my browser or the backend?
<p>This tool directly queries multiple public DNS resolvers from the user's browser (using DoH protocol where supported), representing the resolution results you see locally. Different users in different network environments may see different results due to CDN geo-DNS.</p>
Why do AAAA (IPv6) records sometimes return nothing?
<p>Many domain names don't have IPv6 records configured (no AAAA records); some resolvers may have incomplete IPv6 support or IPv6 routing issues. This is normal — if a domain hasn't deployed IPv6, AAAA queries return empty.</p>
Will CNAME records hide other records?
<p>Yes. Per DNS standards, if a name has a CNAME record, it cannot have other record types (except DNSSEC-related records). When a CNAME exists, resolvers continue resolving the target domain name, returning records of the final target. This is why www subdomains often use CNAME pointing to main domain or CDN domain.</p>
Glossary
- A Record
- Address record, mapping domain names to IPv4 addresses (e.g. example.com → 93.184.216.34). The most commonly used record type.
- AAAA Record
- IPv6 address record, mapping domain names to IPv6 addresses (e.g. example.com → 2606:2800:220:1:248:1893:25c8:1946).
- CNAME Record
- Canonical Name record, pointing one domain name to another domain name (alias). E.g. www.example.com → example.com.
- MX Record
- Mail Exchange record, specifying mail servers receiving email for the domain, with priority values (lower number = higher priority).
- NS Record
- Name Server record, specifying authoritative DNS servers for the domain.
- TXT Record
- Text record, storing arbitrary text information, commonly used for SPF, DKIM, DMARC email verification and domain ownership verification.
- TTL (Time To Live)
- Cache duration in DNS records (seconds), telling resolvers how long to cache before re-querying. Shorter TTL = faster propagation when changing records.
- DoH (DNS over HTTPS)
- DNS over HTTPS protocol, encapsulating DNS queries in HTTPS traffic (port 443), preventing ISP-level DNS hijacking and eavesdropping.
- DoT (DNS over TLS)
- DNS over TLS protocol, encrypting DNS queries using TLS (port 853), providing similar security to DoH with different implementation.
- Recursive Resolver
- Recursive DNS server (also called local DNS), responsible for receiving user query requests and iteratively querying from root/top-level/authoritative servers, returning final results to users.
Common Global Public DNS Resolver Reference
| Resolver Name | IP Address | DoH Support | DoT Support | Operator | Description |
|---|---|---|---|---|---|
| Google DNS | 8.8.8.8 | Yes | Yes | Globally deployed, fast response, supports DoH/DoT | |
| Cloudflare DNS | 1.1.1.1 | Yes | Yes | Cloudflare | Privacy-first, claims not to log user IP |
| Quad9 | 9.9.9.9 | Yes | Yes | Quad9 Foundation | Blocks malicious domains, security protection |
| OpenDNS | 208.67.222.222 | Yes | Yes | Cisco | Supports content filtering and phishing protection |
| 114DNS | 114.114.114.114 | No | No | 114DNS | Domestic high-speed public DNS (China) |
| Ali DNS | 223.5.5.5 | Yes | Yes | Alibaba Cloud | Alibaba Cloud public DNS, domestic nodes |
| Tencent DNS | 119.29.29.29 | Yes | No | Tencent Cloud | DNSPod public DNS, quick domestic resolution |
| Baidu DNS | 180.76.76.76 | No | No | Baidu | Baidu public DNS |
TTL Value Settings and Propagation Time Reference
| TTL Value | Cache Duration | Usage Scenario | Global Propagation Estimate | Notes |
|---|---|---|---|---|
300 | 5 minutes | Emergency migration, pre-change preparation | 5–15 minutes | Increases authoritative DNS query load |
600 | 10 minutes | Planned migration window | 10–30 minutes | Good balance of propagation speed and load |
1800 | 30 minutes | Regular adjustment | 30–60 minutes | General purpose TTL |
3600 | 1 hour | Daily operation default | 1–2 hours | Most commonly used value |
86400 | 24 hours | Long-term stable records | 24–48 hours | Do not set before migration; cache lasts long |
604800 | 7 days | Root domain/NS records | 48–72 hours | Very long cache, only for very stable records |
Authoritative References
- ReferenceRFC 1035 - DNS Domain Name System Standard
- ReferenceRFC 8484 - DNS Queries over HTTPS (DoH)
- ReferenceWikipedia - DNS Propagation
- Authentication Header Generator
- Cache-Control Parser
- Content-Disposition Parser
- CORS Header Generator
- CORS Inspector
- CSP Generator
- cURL to Code Generator
- DNS Propagation Checker
- DNS Lookup
- Forwarded Header Parser
- Hreflang Tag Generator
- HSTS Analyzer
- HTTP Cookie Parser
- HTTP Headers Checker
- HTTP Request Tester
- HTTP Status Codes Lookup
- IP Lookup
- IPv4 Converter
- IPv4 Range Expander
- IPv6 Toolbox
- Link Header Parser
- MX Lookup
- Port Checker
- URL Parameter Builder
- Rate Limit Header Parser
- Redirect Chain Checker
- Robots.txt Generator
- Robots.txt Checker
- Security Headers Checker
- Security.txt Generator
- Set-Cookie Parser
- Site Network Audit
- Sitemap Generator
- Sitemap Inspector
- SSL Certificate Checker
- Subnet Calculator
- URL Parser
- User-Agent Parser
- UTM Link Generator
- WebSocket Tester
- What Is My IP?
- WHOIS Lookup