A network technician is troubleshooting a client workstation that cannot connect to a local server by hostname. To determine where the resolution process fails, arrange the name resolution mechanisms in the exact sequence the host operating system attempts them, from FIRST to LAST.
- 1Inspect the local DNS resolver cache and HOSTS file
- 2Query the configured primary DNS server
- 3Query the configured secondary DNS server
- 4Broadcast an LLMNR or NetBIOS query on the local subnet
Answer
The host operating system resolves names sequentially by checking the local DNS resolver cache and HOSTS file first, sending a query to the primary DNS server second, querying the secondary DNS server third, and broadcasting an LLMNR or NetBIOS query on the local subnet last.
The correct order follows standard operating system host resolution behavior: inspecting local memory resources (DNS cache and HOSTS file) first, followed by configured unicast DNS servers (primary then secondary), and resorting to local subnet link-local resolution (LLMNR/NetBIOS) last.
Step-by-Step Solution
Key Concept
Operating System Name Resolution Order