Recursive resolvers answer on behalf of users and cache results. Authoritative name servers hold the source zone data. Dig can query either one.

Useful dig commands

dig @1.1.1.1 example.com A
dig example.com NS
dig @ns1.example-dns.net example.com A

Troubleshooting checklist

  1. Ask recursive resolvers to see what users may receive.
  2. Ask authoritative servers to see what the DNS provider is publishing.
  3. If authoritative is correct but recursive is old, wait for TTL.
  4. If authoritative is wrong, fix the DNS zone.

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.”