Examkin

DNS Lookup and Name Resolution Roles in Enterprise Networks

18 questions

All types18Multiple choice9Multiple select4Ordering5
Question 1Question →

An enterprise network engineer is analyzing DNS name resolution behavior across internal workstations and external edge firewalls. The infrastructure uses an internal Active Directory DNS server that forwards unknown domain requests to an external resolver. Which two statements correctly describe DNS transport protocol operation and name resolution roles in this environment?

Select all that apply

Show answer & explanation

Answer: Standard DNS queries and responses primarily utilize UDP port 53, but DNS transitions to TCP port 53 when a response payload exceeds 512 bytes (without EDNS0 extensions).; The internal Active Directory DNS server acts as a recursive resolver for enterprise client hosts while functioning as an authoritative server for the local internal domain namespace.

Answer

The correct statements are that DNS queries primarily use UDP port 53 but switch to TCP port 53 when response payloads exceed 512 bytes without EDNS0, and that the internal Active Directory DNS server acts as a recursive resolver for internal clients while being authoritative for the local domain.
The correct options accurately identify that DNS relies primarily on UDP port 53 for standard client lookups, switching to TCP port 53 when responses exceed 512 bytes without EDNS0 extensions. Additionally, they correctly identify that an internal enterprise DNS server serves a dual role: authoritative for internal zone records and recursive resolver for endpoint clients requesting external or un-cached domain names.

Step-by-Step Solution

1
Analyze transport layer protocol usage for DNS queries and responses.
DNS uses UDP port 53 for standard low-overhead queries and responses under 512 bytes. If a response sets the Truncation (TC) bit because it exceeds 512 bytes, the client re-issues the query using TCP port 53.
UDP avoids connection establishment latency for small lookup packets, but TCP provides reliable stream delivery for oversized payloads.
2
Evaluate the distinction between authoritative DNS servers and recursive resolvers.
An internal Active Directory DNS server holds authoritative records for internal resources (such as domain controllers and local hostnames) and resolves non-local queries on behalf of client hosts recursively or via forwarders.
Clients do not query root and TLD servers directly; they rely on their configured recursive resolver to navigate the DNS hierarchy or forward requests.
3
Evaluate incorrect protocol and role assumptions.
Zone transfers require TCP port 53 due to database size and reliability requirements. Clients do not default to TCP port 53 for normal queries, nor do authoritative-only servers perform recursion for external clients.
Distinguishing between control plane operations (zone transfers), data plane lookups (client queries), and server roles (authoritative vs. recursive) clarifies correct DNS architecture.

Key Concept

DNS Transport Protocols and Server Roles in Enterprise Networks
Question 2Question →

An enterprise client workstation sends a DNS name resolution request for an external web service to its local internal Active Directory DNS server. The internal DNS server is configured to perform recursion but does not hold an authoritative zone or a local cached entry for the requested domain name. Which action does the internal DNS server perform to resolve the query for the client workstation?

Show answer & explanation

Answer: It performs iterative queries against external root, top-level domain (TLD), and authoritative DNS servers on behalf of the workstation and returns the final resolution result to the client.

Answer

The internal DNS server performs iterative queries against root, TLD, and authoritative DNS servers on behalf of the workstation and returns the resolved address to the client.
In enterprise network operations, host workstations make recursive DNS queries to an assigned internal DNS server. When the internal DNS server does not possess the record in cache or local authoritative zones, it acts as a recursive resolver by sending a series of iterative queries to external root, TLD, and authoritative servers. Once the final IP address is retrieved, the internal DNS server sends the answer back to the client host.

Step-by-Step Solution

1
Analyze client-to-DNS resolver request type
The client host sends a recursive query to its configured local internal DNS server, delegating the full lookup task to that server.
End-user hosts rely on internal recursive resolvers to handle multi-step domain hierarchy queries.
2
Evaluate internal DNS server cache and authority state
The server has no local zone authority or cached entry for the external domain.
Because it lacks local answers, the recursive server must query external hierarchy servers starting at the root level.
3
Trace external resolution mechanism
The internal DNS server performs iterative requests upstream (Root -> TLD -> Authoritative Server) until obtaining the final record, which it caches and sends back to the client workstation.
This insulates internal clients from direct internet exposure and centralizes enterprise DNS caching.

Key Concept

DNS Recursive Resolver vs Iterative Query Roles in Enterprise Name Resolution
Estimated Time:1m 15s
Question 3Question →

An internal host in an enterprise network queries the corporate DNS server to resolve the Fully Qualified Domain Name (FQDN) of an external cloud service. The internal DNS server does not hold the authoritative zone file for the requested external domain. Assuming standard recursive resolution is enabled on the server, which action does the internal DNS server take to resolve the query for the client?

Show answer & explanation

Answer: It queries external DNS servers on behalf of the host by following the DNS hierarchy until it receives the answer and returns it to the host.

Answer

The internal DNS server queries external DNS servers on behalf of the host by traversing the DNS hierarchy until it receives the answer and returns it to the host.
In enterprise networks, an internal DNS server configured for recursion acts as a recursive resolver for LAN clients. When a host requests resolution for a domain that the server is not authoritative for, the server performs the iterative lookups across external DNS servers (Root, TLD, and Authoritative) on behalf of the client and returns the resolved IP address.

Step-by-Step Solution

1
Analyze the role of a recursive DNS server in enterprise name resolution.
A recursive DNS resolver accepts queries from local host clients and resolves names for domains outside its local authority.
Internal hosts are generally configured to point to an internal recursive resolver rather than querying root internet DNS servers directly.
2
Trace the recursive DNS lookup flow for non-authoritative external domains.
The internal DNS server queries the DNS hierarchy (Root →\rightarrow Top-Level Domain →\rightarrow Authoritative Server) on behalf of the requesting host.
Recursion delegates the responsibility of traversing the global DNS tree to the DNS server rather than forcing the client to issue iterative queries.
3
Return the final response to the host client.
Once the authoritative answer is returned to the enterprise DNS server, it caches the record and sends the IP resolution back to the host.
This process provides seamless name resolution and allows the enterprise server to cache records locally for future requests.

Key Concept

Recursive DNS Query Resolution Flow and Server Roles
Estimated Time:1m 0s
Question 4Question →

An enterprise network administrator is analyzing DNS name resolution behavior across a router configured for local host name lookup. During troubleshooting of large DNS response payloads generated by DNSSEC queries, the administrator notices changes in transport layer protocol utilization. Which two statements correctly describe DNS transport protocol operation and name resolution mechanics in this scenario? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: When a DNS server response exceeds the 512-byte limit standard for traditional UDP DNS messages without EDNS0 extensions, the server returns a response header with the Truncation (TC) bit set, signaling the requesting client to re-query using TCP port 53.; DNS query operations primarily utilize UDP port 53 for low-latency name resolution, but fall back to TCP port 53 for transactions requiring guaranteed delivery or large data transfers such as zone transfers and truncated responses.

Answer

The correct answers state that a DNS response exceeding 512 bytes without EDNS0 sets the Truncation (TC) bit to prompt a re-query via TCP port 53, and that DNS uses UDP port 53 for standard low-overhead queries while utilizing TCP port 53 for large transfers, zone synchronization, and truncated responses.
DNS relies primarily on UDP port 53 for client lookups to minimize network overhead and latency. However, when a UDP DNS response exceeds 512 bytes (without EDNS0), the DNS server sets the Truncation (TC) bit in the header, instructing the client to establish a TCP port 53 connection to retrieve the complete record set. TCP port 53 is also explicitly required for zone transfers between DNS servers.

Step-by-Step Solution

1
Analyze standard DNS transport mechanisms and protocol defaults.
DNS uses UDP port 53 for standard name resolution queries due to connectionless efficiency, while TCP port 53 is used for reliability and data payload requirements exceeding UDP bounds.
Understanding transport protocol selection helps evaluate host and server behavior under varying query conditions.
2
Evaluate the behavior when DNS responses exceed maximum UDP message size limits.
Standard UDP DNS responses cap at 512 bytes. When records (such as DNSSEC or large TXT fields) overflow this boundary without EDNS0 support, the server flags the Truncation (TC) bit in the DNS header.
The TC bit alerts the client that data was omitted and instructs the resolver to re-issue the full query over a stateful TCP connection.
3
Identify misidentifications regarding UDP capabilities and DNS server resolution mechanics.
UDP cannot perform sliding window acknowledgments or dynamic payload adjustments because it lacks header fields for sequencing and flow control.
Eliminates options that attribute TCP connection-oriented mechanisms to UDP.

Key Concept

DNS Transport Protocols and Payload Truncation Mechanics
Question 5Question →

A network administrator is verifying traffic flows from client workstations in an enterprise environment. Which transport layer protocol and destination port does a host client use by default when submitting standard domain name lookup queries to a DNS server?

Show answer & explanation

Answer: UDP port 53

Answer

Standard DNS lookup queries sent by host clients use UDP port 53.
Standard DNS lookup requests from client endpoints rely on UDP port 53 to achieve fast, low-latency name resolution without needing a three-way TCP handshake.

Step-by-Step Solution

1
Identify the application protocol responsible for resolving hostnames into IP addresses.
The Domain Name System (DNS) performs name-to-IP resolution.
Host clients require an IP address to encapsulate data packets destined for named network resources.
2
Determine the transport protocol and port used for standard client queries.
Standard DNS queries use User Datagram Protocol (UDP) on destination port 53.
UDP provides fast, connectionless transmission without connection establishment overhead, making it ideal for quick query-and-response transactions.

Key Concept

DNS Transport Layer Mechanics (UDP Port 53)
Question 6Question →

A network administrator is troubleshooting DNS name resolution in an enterprise network. A client host issues a standard DNS query to an internal recursive DNS server. However, the DNS response payload exceeds 512 bytes because the zone lookup returns a large list of resource records. How does DNS handle transport layer communication when standard UDP responses exceed this size threshold?

Show answer & explanation

Answer: The DNS server responds over UDP with the Truncation (TC) flag bit set to 1, signaling the client to re-query the server using TCP port 53.

Answer

The DNS server responds over UDP with the Truncation (TC) flag bit set to 1, signaling the client to re-query the server using TCP port 53.
Standard DNS operations utilize UDP port 53 for fast, lightweight name resolution queries. When a DNS response message exceeds the traditional 512-byte limit (without EDNS0 extended mechanisms), the DNS server returns a truncated UDP packet with the Truncation (TC) bit set in the DNS header. Receiving this flag prompts the DNS client host to retry the request using a TCP connection on port 53 to successfully receive the complete response.

Step-by-Step Solution

1
Analyze transport protocols used by DNS
DNS uses UDP port 53 for normal queries/responses due to low overhead, but uses TCP port 53 for zone transfers and responses exceeding traditional size limits.
Traditional DNS over UDP limits message payloads to 512 bytes (unless EDNS0 extensions are negotiated).
2
Determine how DNS signals payload overflow
When a response message is too large for a single 512-byte UDP packet, the DNS server sets the TC (Truncated) bit in the DNS header.
Setting the TC bit informs the resolver client that only partial data was delivered and full data requires a TCP connection.
3
Identify client fallback behavior
Upon receiving the TC bit set in a UDP response, the DNS client opens a connection to TCP port 53 on the DNS server to re-issue the query.
TCP provides connection-oriented reliability and supports larger payload data transfers without truncation.

Key Concept

DNS Transport Layer Mechanics (UDP vs TCP Port 53 and Truncation)
Question 7Question →

An enterprise workstation is configured with a primary DNS server address of 10.10.20.5. The user attempts to access an external website by entering `service.partnercloud.com` into a web browser. The internal DNS server (10.10.20.5) is operational and has recursion enabled, but it currently has no cached record or authoritative zone file for `partnercloud.com`. Which statement accurately describes the name resolution role and process performed by the internal DNS server to resolve this request?

Show answer & explanation

Answer: The internal DNS server acts as a recursive resolver for the client, sending iterative queries to external root, TLD, and authoritative name servers on the client's behalf, and then returns the final IP address to the workstation.

Answer

The internal DNS server acts as a recursive resolver for the client, issuing iterative queries to root, TLD, and authoritative DNS servers on behalf of the workstation, and returning the resolved IP address to the client.
In enterprise network operations, host computers act as stub resolvers that issue recursive queries to their designated internal DNS server. When the local DNS server lacks an authoritative zone or cached entry for a domain, it assumes the role of a recursive resolver: it queries external DNS servers (root hints, TLD servers, and domain authoritative servers) iteratively on behalf of the client and returns the resolved IP address back to the workstation.

Step-by-Step Solution

1
Identify the type of query originated by the client workstation.
The workstation sends a recursive DNS query to its configured local DNS server (10.10.20.5).
Standard client operating systems perform recursive lookups, delegating the entire resolution workflow to their designated local resolver.
2
Determine the local DNS server's cache and authoritative state.
The server has no cached entry and is not authoritative for `partnercloud.com`.
Because the answer is not cached or stored locally, the server must query external hierarchy nodes.
3
Trace the server-side lookup process.
The local server issues iterative queries starting at the DNS root servers, progressing to the TLD servers (.com), and finally querying the authoritative server for `partnercloud.com`.
Recursive resolvers execute iterative queries on behalf of the requesting host to obtain the final answer.
4
Complete the resolution back to the host.
The local DNS server caches the answer and sends an A record response containing the IP address to the workstation.
The client receives a single final answer directly from its local DNS server.

Key Concept

DNS Recursive vs. Iterative Query Roles in Enterprise Networks
Estimated Time:1m 30s
Question 8Question →

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.

Drag items to arrange them in the correct order

Show answer & explanation

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

1
Check local client sources
Host determines whether the mapping is already known in local memory or local configuration files.
Checking local host cache avoids unnecessary network overhead.
2
Initiate DNS request
Host transmits a UDP packet to port 53 of the primary DNS server.
The client delegates full resolution responsibility to its recursive resolver.
3
Perform recursive server lookup
The internal DNS server communicates with authoritative DNS infrastructure.
The recursive server traverses the DNS hierarchy to find the authoritative answer.
4
Deliver and cache response
The workstation receives the IP address and completes establishing connection to the destination.
Caching speeds up future resolution queries within the TTL period.

Key Concept

DNS Lookup Process and Name Resolution Roles
Question 9Question →

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.

Drag items to arrange them in the correct order

Show answer & explanation

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
Question 10Question →

In an enterprise network environment, host computers rely on various network services to locate resources efficiently. Which fundamental role is performed by a Domain Name System (DNS) server during host-to-host communications?

Show answer & explanation

Answer: Mapping human-readable hostnames to their corresponding network IP addresses

Answer

The correct role performed by a DNS server is mapping human-readable hostnames to their corresponding network IP addresses.
The option stating 'Mapping human-readable hostnames to their corresponding network IP addresses' is correct because DNS serves as the protocol responsible for resolving computer hostnames and domain names into IP addresses so that network devices can route traffic to the intended destination.

Step-by-Step Solution

1
Identify the primary requirement
Network protocols require numerical IP addresses for routing packets across networks, but users use hostnames.
Host computers need a mechanism to convert friendly hostnames into layer 3 IP addresses.
2
Evaluate the role of DNS
DNS operates as a distributed database providing name-to-address resolution.
When a host queries a DNS server with a name, the server responds with the matching A or AAAA record containing the destination IP address.

Key Concept

DNS Name Resolution
Question 11Question →

An administrator is reviewing DNS lookup behaviors and transport protocol characteristics for enterprise host name resolution. Which two statements correctly describe DNS operations and protocol roles during name resolution? (Choose two.)

Select all that apply

Show answer & explanation

Answer: Standard client DNS query requests and small responses typically use UDP port 53 to reduce latency and header overhead.; DNS switches to TCP port 53 when a response payload exceeds the standard buffer limit or during zone transfers between DNS servers.

Answer

Standard client DNS queries primarily use UDP port 53 to minimize transport overhead, but DNS fallback to TCP port 53 occurs when response sizes exceed buffer limits or during server-to-server zone transfers.
DNS queries use UDP port 53 by default because connectionless transport reduces overhead and latency for simple lookups. When response data exceeds standard message length thresholds or during DNS zone transfers between servers, DNS relies on TCP port 53 for reliable connection-oriented delivery.

Step-by-Step Solution

1
Identify standard DNS transport behavior for general host queries.
DNS uses UDP port 53 for simple queries and responses to maintain low connection establishment overhead and quick lookups.
UDP is connectionless and optimized for lightweight request-response exchanges.
2
Identify conditions where DNS uses TCP instead of UDP.
TCP port 53 is used when response messages are truncated (exceeding standard UDP buffer size) or during bulk data synchronization such as zone transfers.
TCP provides reliable, stream-oriented delivery for large payloads or state transfers.

Key Concept

DNS Transport Protocols and Server Resolution Roles
Question 12Question →

A network administrator is evaluating the operation of DNS protocol mechanisms and transport layer behavior within an enterprise network infrastructure. Which two statements accurately describe how DNS lookup processes and transport protocols function during name resolution? (Choose two.)

Select all that apply

Show answer & explanation

Answer: Standard DNS queries for IP address resolution (A or AAAA records) typically utilize UDP port 53 to reduce latency and connection overhead.; When a DNS response payload exceeds 512 bytes without EDNS0 support, the server sets the TrunCation (TC) bit, prompting the client to re-query using TCP port 53.

Answer

The two correct statements are that standard DNS queries for IP address resolution typically utilize UDP port 53 to reduce latency, and when a DNS response payload exceeds 512 bytes without EDNS0 support, the server sets the TrunCation (TC) bit to prompt the client to re-query using TCP port 53.
Standard DNS lookups operate over UDP port 53 because single-packet requests and responses do not warrant the overhead of a TCP connection. However, if a DNS response message is truncated due to exceeding 512 bytes (without extension mechanisms like EDNS0), the DNS server sets the TC (TrunCation) bit in the header. Upon receiving a truncated response, the client initiates a TCP connection on port 53 to reliably retrieve the complete set of resource records.

Step-by-Step Solution

1
Identify the primary transport protocol used for standard DNS queries.
DNS uses UDP port 53 for normal client-to-server and server-to-server queries to maintain low latency and minimize connection overhead.
Establishing a TCP connection for small request/response pairs adds unnecessary delay.
2
Determine the conditions under which DNS transitions from UDP to TCP transport.
DNS falls back to TCP port 53 when the response exceeds 512 bytes (indicated by the TC bit in the DNS header) or during DNS zone transfers (AXFR/IXFR).
TCP guarantees reliable delivery and reassembly for large payloads that cannot fit into standard UDP DNS packets.

Key Concept

DNS Transport Protocols and TrunCation (TC) Mechanism
Question 13Question →

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.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

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.

Step-by-Step Solution

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.

Key Concept

DNS Resolution Hierarchy and Iterative vs Recursive Query Roles
Question 14Question →

An enterprise network engineer configures an internal host to resolve domain names via a local Active Directory DNS server, which is configured to forward external queries to a public DNS resolver. During a packet capture analysis on the firewall boundary, the engineer observes that a specific DNS query originating from the internal AD DNS server towards an external authoritative DNS server for a large DNSSEC-signed domain initially uses UDP destination port 53, receives a response with the TrunCation (TC) bit set to 1, and immediately follows up with a new request to the same target server using TCP destination port 53. Which statement accurately explains the fundamental reason for this protocol switch during the name resolution process?

Show answer & explanation

Answer: The DNS server switches to TCP because the response payload exceeds the negotiated maximum transmission unit (or 512-byte traditional UDP DNS limit), requiring TCP stream reliability to reassemble and guarantee delivery of large resource record sets.

Answer

The DNS server switches to TCP port 53 because the DNS response payload exceeds the maximum supported UDP DNS buffer size, causing the responder to set the TrunCation (TC) bit and prompting the requester to re-query over TCP.
Standard DNS operations use UDP port 53 for fast, lightweight name resolution. However, when a DNS answer payload (such as large DNSSEC resource record sets) exceeds the supported UDP datagram size limit, the responding server truncates the response and sets the TrunCation (TC) flag bit in the DNS header. When the querying DNS entity detects TC=1, standard DNS behavior dictates establishing a TCP connection to port 53 and re-transmitting the query to receive the full, untruncated answer payload.

Step-by-Step Solution

1
Analyze the DNS packet capture details
Identified that the initial UDP query returned a DNS response with the TC (TrunCation) bit set to 1.
The TC bit indicates that the responding server truncated the answer because the payload exceeded the maximum allowable DNS UDP message size.
2
Evaluate transport layer behavior for DNS
DNS operates primarily over UDP port 53 for speed, but falls back to TCP port 53 when responses are truncated.
TCP provides stream-based transmission capable of handling payload sizes larger than the single-datagram UDP limit without losing data integrity.
3
Select the option that correctly describes TC bit functionality and TCP fallback
Confirmed that payload overflow leading to TC=1 triggers an immediate retry over TCP port 53.
This is a core DNS specification behavior defined in RFC 1035 and enhanced by EDNS0.

Key Concept

DNS Transport Layer Mechanics and TC Bit Truncation Fallback
Estimated Time:2m 0s
Question 15Question →

An enterprise host needs to resolve the IP address of an internal web application server (app.corp.local) after the local cache has expired. Place the steps of the name resolution process in the correct chronological order from first to last.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of DNS name resolution steps is: 1) The host checks its local OS DNS client resolver cache and local hosts file. 2) The host encapsulates a recursive DNS query in a UDP datagram with destination port 53 and sends it to its primary configured DNS server. 3) The enterprise DNS server receives the query and checks its authoritative DNS zones. 4) The DNS server formulates an authoritative response packet containing the requested A record. 5) The host receives the DNS response packet and stores the IP address mapping in its local DNS resolver cache.
The correct order follows the standard host-to-server DNS name resolution flow: first, local host resources (cache and hosts file) are inspected. If unresolved, the client sends a recursive UDP query (destination port 53) to its configured local DNS server. The DNS server processes the query against its zone database, generates an authoritative response containing the A record, and returns it to the host. Finally, the host receives the response and caches the IP address locally.

Step-by-Step Solution

1
Evaluate local host resolution mechanisms.
Local resolver cache and hosts file are queried first prior to generating outbound network requests.
Checking local host memory avoids unnecessary network traffic and reduces latency.
2
Transmit DNS request over the local network connection.
A UDP datagram targeted to destination port 53 is forwarded to the designated local DNS server.
Standard DNS queries use UDP port 53 for low-overhead client-to-server communications.
3
Process query at the targeted enterprise DNS server.
The server checks its local authoritative zone files for matching domain records.
Because the domain is internal (corp.local), the internal DNS server acts as the authoritative source.
4
Build DNS server response payload.
An authoritative DNS answer payload containing the IPv4 (A) record is created.
The server must supply the mapped IP address back to the requesting client.
5
Process response on the requesting client host.
The client receives the response and caches the entry according to the record's Time-to-Live (TTL).
Caching allows subsequent applications on the host to reuse the resolved IP address without repeating the DNS lookup.

Key Concept

Client DNS resolution sequence and DNS server roles
Question 16Question →

A network administrator configures the IP address of an external DNS server on a Cisco IOS router using the command `ip name-server 10.1.1.1`. However, when attempting to ping a remote server by its hostname (`ping server1.example.com`), the router immediately fails to resolve the name and no DNS query packets are transmitted. Which command must be entered in global configuration mode to enable the router to perform DNS queries for hostname resolution?

Show answer & explanation

Answer: ip domain lookup

Answer

The command `ip domain lookup` must be configured in global configuration mode to enable Cisco IOS DNS hostname resolution.
The `ip domain lookup` command globally enables the DNS host name resolution feature on a Cisco IOS router. Without this command enabled, the router will not generate DNS request packets to configured DNS servers specified by `ip name-server`.

Step-by-Step Solution

1
Identify the role of the Cisco IOS device in name resolution
The router is acting as a DNS client trying to resolve hostnames to IP addresses for local CLI operations.
Configuring `ip name-server` defines the destination DNS server IP address, but the DNS lookup process must be globally enabled on the device.
2
Determine the global command required to enable client DNS lookups
Executing `ip domain lookup` enables the IP DNS client feature in Cisco IOS.
If DNS lookup is disabled (via `no ip domain lookup`), Cisco IOS will not initiate DNS queries over UDP port 53 even if valid name servers are defined.

Key Concept

Cisco IOS DNS Client Configuration and Hostname Resolution Mechanics
Question 17Question →

An enterprise client workstation attempts to access an external web application at `app.partner.example.net` for the first time. Arrange the steps of the complete DNS resolution process in the correct chronological order, starting from the client's initial lookup request to the final IP address retrieval.

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence begins with the client host checking its local resolver cache and hosts file, followed by sending a recursive query to the local internal DNS resolver. The internal resolver then performs iterative queries starting at the root server, proceeding to the .net TLD server, and finally querying the authoritative server for partner.example.net before caching the record and returning the resolved IP address to the client.
The proper sequence follows standard operating system and DNS protocol operational order: local client cache and hosts file check -> client recursive query to the local internal DNS resolver -> internal resolver iterative query to the root name server -> root referral to the TLD server -> TLD referral to the domain authoritative server -> authoritative answer returned, cached by the internal resolver, and forwarded to the client.

Step-by-Step Solution

1
Check local OS resolution mechanisms.
The host OS scans the local `hosts` file and client DNS cache for `app.partner.example.net`.
Local lookup prevents unnecessary network overhead if the IP address is already known locally.
2
Transmit recursive query from client host to configured DNS server.
A UDP port 53 recursive query is sent to the internal enterprise DNS resolver.
The client delegates name resolution responsibility entirely to its configured local DNS server.
3
Initiate iterative resolution from the DNS root hierarchy.
The internal DNS server queries a DNS root hint server (`.`).
When resolving an un-cached external FQDN, the recursive resolver starts lookups at the root zone.
4
Process root referral response.
The root server responds with NS and glue A records for the `.net` TLD servers.
Root servers maintain delegation points for top-level domains.
5
Query TLD name server for domain authority.
The `.net` TLD server provides NS records pointing to authoritative servers for `partner.example.net`.
TLD servers maintain delegations for secondary registered domains under their top-level domain.
6
Fetch definitive record from authoritative server and respond to client.
The authoritative server responds with the `A` record, which the internal server caches and forwards to the requesting client.
Only authoritative name servers hold the master resource records for the targeted domain.

Key Concept

DNS Lookup and Name Resolution Roles in Enterprise Networks
Estimated Time:2m 0s
Question 18Question →

An enterprise network engineer observes that a Cisco IOS device attempting to resolve a hostname receives a DNS response from the DNS server with the Truncation (TC) bit set in the DNS header. Which action does the client device perform to obtain the complete set of resource records?

Show answer & explanation

Answer: It initiates a TCP connection to the DNS server on port 53 and re-issues the lookup request.

Answer

The client device initiates a TCP connection to the DNS server on port 53 and re-issues the lookup request.
Standard DNS transactions utilize UDP port 53 due to lower overhead. However, basic UDP DNS responses are restricted to a maximum size of 512 bytes. If the answer exceeds this size limit, the DNS server sets the Truncation (TC) bit in the DNS header. When a client receives a response with the TC bit set, it recognizes that data was omitted and re-issues the query over a TCP connection to port 53, allowing the full set of resource records to be transferred reliably.

Step-by-Step Solution

1
Analyze standard DNS transport protocol limits.
Standard DNS resolution operates over UDP port 53 with a maximum message size limit of 512 bytes to minimize network overhead.
UDP provides fast name resolution without requiring connection setup state.
2
Identify the purpose of the DNS Truncation (TC) bit.
When a DNS response payload exceeds 512 bytes, the responding DNS server sets the TC bit to 1 in the DNS response header.
This signals to the client that the returned data was truncated and incomplete.
3
Determine the RFC-compliant DNS client behavior upon receiving a truncated response.
The client opens a reliable TCP connection to the same DNS server on port 53 and re-sends the query.
TCP streaming handles large payloads by managing segmentation and reliable delivery without the 512-byte restriction.

Key Concept

DNS Transport Protocols and Truncation Mechanics (UDP vs TCP Port 53)
Estimated Time:1m 30s