Dig asks DNS a specific question and prints the answer. That makes it one of the cleanest ways to see how a domain name becomes an IP address, mail route, verification record, or delegated zone.
When to use this check
Dig asks DNS a specific question and prints the answer. That makes it one of the cleanest ways to see how a domain name becomes an IP address, mail route, verification record, or delegated zone.
Use a dig lookup when you need to see the DNS answer itself, not a browser error or a control-panel summary. DNS answers can differ by record type, resolver cache, and delegation path.
Useful commands
dig example.com NS
dig example.com SOAWhat to look for
- The record value matches the provider instructions or migration plan.
- The TTL is reasonable for the timing of the change.
- The answer is coming from the expected name or target.
- There are no unexpected empty answers, stale values, or conflicting records.
Common mistakes
The most common mistake is checking the wrong name. For example, example.com, www.example.com, mail.example.com, and _dmarc.example.com are separate DNS names. Query the exact name used by the application or provider instructions.
How to use the result
Compare the dig result with your source of truth: DNS provider zone, registrar delegation, hosting instructions, email provider setup page, certificate authority challenge, or infrastructure documentation. If the DNS answer is wrong, fix DNS first. If the DNS answer is correct, continue troubleshooting the next layer.