Question

Difficulty: MediumDNS Lookup and Name Resolution Roles in Enterprise Networks

An enterprise workstation attempts to connect to an external service by domain name (web.example.com) for the first time. Arrange the following DNS lookup and name resolution steps in the correct sequential order from the client's initial request to receiving the final IP address.

  1. 1The workstation checks its local operating system DNS resolver cache and local hosts file.
  2. 2The workstation transmits a recursive DNS query to its configured local enterprise DNS resolver over UDP port 53.
  3. 3The enterprise DNS resolver sends an iterative query to a DNS Root Name Server to determine the Top-Level Domain (TLD) server.
  4. 4The enterprise DNS resolver queries the designated TLD Name Server to obtain the IP address of the domain's authoritative server.
  5. 5The enterprise DNS resolver queries the Authoritative Name Server for example.com to retrieve the final A record.

Answer

The correct chronological sequence is: local cache/hosts file check, recursive query to configured enterprise DNS resolver over UDP port 53, iterative query to Root Name Server, iterative query to TLD Name Server, and finally iterative query to Authoritative Name Server for the host IP mapping.
DNS resolution begins locally on the host by evaluating local memory cache and hosts file entries. If unmapped, the host issues a recursive request over UDP port 53 to its configured enterprise DNS resolver. The resolver then carries out iterative queries starting at the Root level, proceeding to the TLD server level, and finally reaching the Authoritative server that returns the definitive resource record mapping.

Step-by-Step Solution

1
Evaluate local host cache
Workstation verifies if web.example.com exists in local resolver cache or local hosts file.
Checking local host cache avoids unnecessary network traffic and speeds up resolution.
2
Issue client recursive query
Workstation sends a DNS query to the designated local DNS server asking it to complete the full lookup.
Clients use recursive queries so the local DNS server takes responsibility for traversing the DNS hierarchy.
3
Query Root server
Enterprise DNS server contacts a Root Name Server.
Root servers provide referrals to the Top-Level Domain (TLD) servers responsible for extensions such as .com.
4
Query TLD server
Enterprise DNS server queries the TLD server for .com.
TLD servers store information pointing to the specific domain's authoritative name servers.
5
Query Authoritative server
Enterprise DNS server queries the Authoritative server for example.com and gets the host IP address (A record).
Authoritative servers contain the actual DNS resource records for hosts in their managed domain zone.

Key Concept

DNS Name Resolution Mechanics and Server Roles
Rate this question