Resolver comparison helps identify cache differences, ISP resolver issues, and regional DNS inconsistencies.

Useful dig commands

dig @1.1.1.1 example.com A
dig @8.8.8.8 example.com A
dig @9.9.9.9 example.com A

Troubleshooting checklist

  1. Use the same name and type for each resolver.
  2. Record the returned value and TTL.
  3. Check authoritative DNS if resolvers disagree for too long.
  4. Do not compare different record types and treat them as the same test.

How to interpret the result

If the answer matches the expected value, DNS is probably not the layer causing the current symptom. Continue with HTTP, TLS, mail server, firewall, or application checks. If the answer is missing, stale, or different between resolvers, keep the investigation in DNS until the public answer is correct.

Support note

When opening a ticket with a DNS provider, include the exact name, record type, resolver tested, returned value, and time of the lookup. That is much more useful than saying “DNS is not working.”