When people say DNS is propagating, they usually mean resolver caches are expiring at different times. Dig helps you see whether authoritative DNS has the new value and which public resolvers still have the old one.

Useful dig commands

dig example.com NS
dig @ns1.provider.net example.com A
dig @1.1.1.1 example.com A
dig @8.8.8.8 example.com A

Troubleshooting checklist

  1. Query the authoritative name server directly.
  2. Query several public recursive resolvers.
  3. Compare the returned TTL values.
  4. Wait for the old TTL to expire before assuming the change failed.

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