A DNS change can be correct in the provider dashboard and still not appear everywhere. The usual cause is caching, but delegation and zone mistakes are also common.

Useful dig commands

dig example.com NS
dig @authoritative-ns.example example.com A
dig @1.1.1.1 example.com A

Troubleshooting checklist

  1. Check the authoritative server first.
  2. Check at least two public resolvers.
  3. Compare the answer with the old value.
  4. Read TTL instead of guessing.
  5. Confirm the registrar points at the intended name servers.

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