Examkin

Soru

Zorluk: ZorDNS Lookup and Name Resolution Roles in Enterprise Networks

An enterprise client host without a cached DNS entry needs to connect to an external server using its domain name. Place the steps of the full name resolution flow in the correct chronological order, starting from the client's initial lookup request to the final response delivery.

  1. 1The client host checks its local DNS cache and hosts file, finds no entry, and transmits a recursive DNS query to its configured internal enterprise DNS server.
  2. 2The internal enterprise DNS server receives the query and sends an iterative DNS query to a root name server, receiving a referral response pointing to the appropriate Top-Level Domain (TLD) servers.
  3. 3The internal enterprise DNS server issues an iterative query to the TLD name server and receives a referral response containing the IP addresses of the target domain's authoritative name servers.
  4. 4The internal enterprise DNS server queries the authoritative name server for the target domain and receives the authoritative answer containing the host's IP address.
  5. 5The internal enterprise DNS server saves the resolved resource record into its local cache and forwards the DNS response message to the client host.

Cevap

The correct chronological sequence begins with the client host issuing a recursive query to the internal DNS server after checking its local cache. Next, the internal DNS server executes iterative lookups starting at a root DNS server, followed by the TLD DNS server, and finally the domain's authoritative DNS server. Upon receiving the A/AAAA record from the authoritative server, the internal DNS server caches the result and delivers the IP address to the requesting client.
The correct order follows the standard hierarchy of enterprise DNS name resolution. First, the client checks its local cache and queries its local DNS server recursively. Second, if un-cached, the internal recursive DNS server initiates iterative lookups starting at the root servers. Third, the root server redirects the query to the TLD server. Fourth, the TLD server refers the query to the authoritative name server. Fifth, the authoritative name server provides the IP mapping, which the internal server caches before replying to the client host.

Adım Adım Çözüm

1
Evaluate host-level resolution steps
Client host checks local cache/hosts file, then sends a recursive lookup request to the configured internal DNS server.
Hosts must exhaust local name resolution mechanisms before querying network resolvers over port 53.
2
Trace top-of-hierarchy DNS server lookup
Internal recursive server queries a Root name server and receives a referral to the TLD name servers.
Iterative resolution moves top-down through the domain namespace starting at the root (".").
3
Trace mid-hierarchy DNS server lookup
Internal recursive server queries the TLD server (such as .com) and receives a referral to the authoritative name server.
TLD servers delegate authority for specific subdomains to organizational name servers.
4
Trace authoritative response acquisition
Internal recursive server queries the domain's authoritative name server and receives the final mapping.
Only the authoritative DNS server for a domain holds the definitive zone file records.
5
Complete recursive loop to client
Internal recursive server caches the mapping according to TTL and returns the resolved address to the client.
The client receives a single final response to satisfy its initial recursive query.

Anahtar Kavram

DNS Resolution Hierarchy and Iterative vs Recursive Query Roles
Bu soruyu puanla

Konular

DNS Lookup and Name Resolution Roles in Enterprise Networks

Bu konudan daha fazla soru