TTL is the timer that tells resolvers how long they may cache a DNS answer. Reading TTL correctly prevents wasted troubleshooting.

Useful dig commands

dig example.com A
dig @1.1.1.1 example.com A

Troubleshooting checklist

  1. A low TTL helps during planned changes.
  2. A high TTL means old records may remain visible longer.
  3. Changing TTL after a mistake does not immediately clear old caches.
  4. Authoritative TTL and remaining resolver TTL are related but not always the same number.

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