Use dig to follow delegation from the root to authoritative servers instead of asking a recursive resolver for only the final answer.
Which command is appropriate?
dig +trace starts at root servers and follows referrals iteratively until it reaches an authoritative answer.
Detailed explanation
dig +short example.test AIncorrect. +short only changes output formatting.
Incorrect. +short only changes output formatting.
dig +trace example.test ACorrect. It traces delegation from the root servers.
Correct. It traces delegation from the root servers.
dig +tcp example.test AIncorrect. +tcp changes transport but does not enable delegation tracing.
Incorrect. +tcp changes transport but does not enable delegation tracing.
dig +noall example.test AIncorrect. +noall suppresses sections but does not perform a trace.
Incorrect. +noall suppresses sections but does not perform a trace.
Try it yourself
An example you can run in a temporary verification environment.
printf '%s
' '+trace -> root, TLD, authoritative delegation path'Expected result
+trace -> root, TLD, authoritative delegation pathKey points
- Use +trace
- Follow delegation iteratively
- Different from +short and +tcp
Notes
- Environment: dig option対応表（DNS通信なし）
- Command output formatting can vary slightly by distribution or tool version.
- Run the example in a temporary directory or process when possible.
Foundation review
Read the scope first
Check whether the command acts on the current shell, a new process, an existing process, or a file.
Verify the observable result
Use the supplied command and compare the output with the expected result.