Changing name servers at the registrar changes who is authoritative for the domain. Dig helps verify whether the public delegation has moved.

Useful dig commands

dig example.com NS
dig +trace example.com
dig @new-ns.example.net example.com SOA

Troubleshooting checklist

  1. Check NS at the parent delegation.
  2. Check SOA from the new provider.
  3. Confirm records exist in the new zone before switching.
  4. Keep old DNS running until traffic has moved.

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