Network and IP Planning · #22
Online DNS Resolver Comparison
Compares a name's answer from two public resolvers; shows content differences and TTLs separately.
- Live DNS query (Cloudflare DNS over HTTPS)
Tool
What does this tool do?
After a DNS change some users reach the new address and others the old one, because resolvers keep the old answer until the TTL expires. The tool sends the same query to Cloudflare and Google and compares the record sets. Records may come in a different order; that is not a difference.
How to use it
- Choose name and record type and press Run.
Fields
- Name
- Record type
Worked example
| Input | Value |
|---|---|
| Name | www.contoso.com |
| Record type | A |
Expected result: Both resolvers return the same two A records in reverse order → equal content; different TTLs (300 and 211).
Different order is normal with round-robin. The different TTL shows Google cached the record earlier; a change becomes visible on both after that time.
Method and assumptions
Each resolver's answer set is lower-cased, trailing dots removed, TXT segments joined and sorted. If status codes and sets match, the answers are 'equal'.
TTL is not compared; it shows the remaining cache time and naturally differs.
Using the result and troubleshooting
If content differs, wait for the old TTL to pass. If it persists, check whether the authoritative servers (NS) are consistent.
Limits and common mistakes
- Only two fixed public resolvers are compared; ISP and corporate resolvers are out of scope.
- Names that answer by geography or EDNS client subnet (GeoDNS) are expected to differ.
Frequently asked questions
Can I speed up propagation?
Only by lowering the TTL before the change (e.g. 300 seconds); resolver caches cannot be flushed from outside. Cloudflare and Google offer their own cache purge pages.
Related tools and service
- DNS LookupFetches the DNS records of one name and type from a public resolver, with TTLs.
Related service: Network Performance Analysis and Troubleshooting