A client workstation on a corporate network initiates a web connection to `service.partner.org`. Assuming no DNS records are cached on the client or intermediate servers, place the following DNS resolution steps in the correct chronological order from the initial request to the final address delivery.
- 1The client stub resolver issues a recursive DNS query for `service.partner.org` to the local configured DNS resolver.
- 2The local DNS resolver queries a DNS Root Name Server and receives a referral to the `.org` Top-Level Domain (TLD) name servers.
- 3The local DNS resolver queries a `.org` TLD Name Server and receives a referral to the authoritative name servers for `partner.org`.
- 4The local DNS resolver queries an authoritative name server for `partner.org` and receives the A record containing the IP address for `service.partner.org`.
- 5The local DNS resolver caches the IP address mapping and returns the DNS response to the client stub resolver.
Answer
The correct chronological sequence begins with the client stub resolver querying the local recursive resolver. The local resolver then performs iterative lookups by querying the Root Name Server, followed by the `.org` TLD Name Server, and finally the Authoritative Name Server for `partner.org`. Lastly, the local resolver caches the record and returns the IP address to the client.
In standard DNS architecture, name resolution follows a hierarchical top-down lookup pattern when un-cached. The client host sends a recursive query to its local DNS server. The local DNS server then performs iterative queries starting at the Root servers (top level), proceeding to the TLD servers (`.org`), and ending at the domain's Authoritative servers (`partner.org`). Finally, the local server caches the answer and forwards it back to the client host.
Step-by-Step Solution
Key Concept
Recursive and Iterative DNS Resolution Flow