An enterprise workstation needs to access a web server using its Fully Qualified Domain Name (FQDN). Arrange the steps of the DNS name resolution process in the correct chronological order from first to last.
- 1The host checks its local DNS cache and hosts file for an existing name-to-IP mapping.
- 2The host sends a recursive DNS query over UDP port 53 to its configured DNS server.
- 3The recursive DNS server queries external name servers (Root, TLD, and Authoritative) to resolve the FQDN.
- 4The recursive DNS server returns the resolved IP address to the workstation and caches the record.
Answer
The correct sequence of DNS name resolution begins with the client checking its local resolver cache and hosts file, followed by sending a recursive query to the configured DNS server on UDP port 53. The DNS server performs iterative lookups against authoritative root, TLD, and domain servers, and finally returns the resolved IP address back to the requesting workstation.
The name resolution process follows a strict hierarchy. First, local system resources (cache and hosts file) are inspected. If unresolved, the client generates a recursive DNS query to its configured DNS server via UDP port 53. The DNS server resolves the query via external hierarchy (Root, TLD, Authoritative servers) as needed, and lastly sends the reply back to the workstation while saving the mapping in its local cache.
Step-by-Step Solution
Key Concept
DNS Lookup Process and Name Resolution Roles