Command Syntax

dig [name] [type] @[resolver] [+short] [+trace]

What It Does

Performs detailed DNS queries with protocol-level response metadata.

When to Use It

Use for authoritative truth, resolver comparisons, and delegation tracing.

Example Output

Headers show status and flags while sections show answer, authority, and additional records.

How to Interpret Results

Prioritize status code, AA/AD flags, TTL values, and trace path behavior.

How DNS Panopticon Detects This

  • Relevant checks: Delegation integrity, resolver consistency, DNSSEC health, and suspicious record-pattern checks.
  • Severity mapping: Informational, medium/high, or critical based on exploitability and user impact.
  • Score impact: Reliability and security scoring dimensions are reduced according to blast radius.
  • Related findings users will see: NS drift, validation failure, orphaned CNAMEs, wildcard exposure, and policy misconfiguration alerts.

Operator Checklist

  • Verify behavior from at least two public resolvers and one resolver inside your own network before making changes.
  • Make one change at a time, capture before/after query output, and wait for TTL windows to clear so you can confirm impact.
  • Document the root cause and the final fix in your runbook to shorten future incidents.