A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
DNS reconnaissance is valuable because names often reveal application structure, mail systems, service discovery, and routing clues. `dig` is the precise query tool: it lets you choose record types and inspect response details. `getent hosts` exercises the system name-service path, which can involve sources other than DNS depending on `/etc/nsswitch.conf`.
Do not assume that an answer came straight from the authoritative server. Your configured resolver may answer from cache, synthesize data, or apply policy. When a record matters to an investigation, query deliberately and preserve the server and record type in your evidence.
Requests a concise IPv4 address answer for the lab hostname when the local resolver has the record. The useful habit here is to treat the command output as evidence about one system fact, not as a magical diagnosis.
The command output shown here is a training fixture description. On a live system, verify the actual output rather than assuming it matches the example.
Some environments publish split-horizon DNS, so the answer seen from one network may differ from another. That is not necessarily an error. Treat resolver location and source as part of the observation. In a lab, use the declared network and private names rather than probing unrelated public infrastructure.
Uses the host lookup path configured by the operating system. Read the result in context: the same command can be correct yet insufficient if a permission boundary, alternate configuration, or different backend changes what it reports.
A practitioner’s checkpoint: compare the observed behavior with the assumption your script is about to make. If the assumption is broader than the evidence, narrow the rule. If the evidence is incomplete, report the uncertainty instead of converting it into a confident finding.
DNS results describe a resolver’s view. Preserve the query type and resolver context when the observation matters.
Lab discipline: stay inside the declared course environment, prefer read-only checks for learning exercises, and preserve the original output of security tools before transforming it.
Finish the lesson once you have worked through the material. This awards ★ 35 XP.