A client workstation attempts to resolve the domain name `www.example.com`, which is not stored in any local cache. Arrange the steps of the un-cached recursive DNS resolution process in the correct chronological order from first to last.
- 1The client stub resolver sends a recursive query for `www.example.com` to its configured local recursive DNS resolver.
- 2The local recursive resolver queries a Root Name Server to obtain the referral IP address for the `.com` Top-Level Domain (TLD) name server.
- 3The local recursive resolver queries the `.com` TLD Name Server to get the authoritative name server IP address for `example.com`.
- 4The local recursive resolver queries the authoritative name server of `example.com` to retrieve the `A` record for `www.example.com`.
- 5The local recursive resolver caches the resource record and returns the resolved IP address to the client stub resolver.
Cevap
The correct chronological sequence begins with the client stub resolver querying the local recursive resolver, followed by iterative queries from the recursive resolver to the Root Name Server, the TLD Name Server, and the Authoritative Name Server, ending with the recursive resolver caching the record and sending the IP address back to the client.
The standard DNS resolution flow follows a strict top-down traversal when host cache is empty: Stub Resolver → Recursive Resolver → Root Name Server → TLD Name Server → Authoritative Name Server → Recursive Resolver (cache & reply) → Client.
Adım Adım Çözüm
Anahtar Kavram
Recursive DNS Resolution Hierarchy