Examkin

Soru

Zorluk: ZorDNS Lookup and Name Resolution Roles in Enterprise Networks

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.)

  1. 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.Cevap
  2. 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.Cevap
  3. C
    If a UDP DNS packet payload is truncated, the UDP transport protocol utilizes native sequence numbers and dynamic windowing to retransmit only the missing resource record fields without switching protocols.
  4. D
    When a DNS response payload exceeds the path MTU, the requesting host sends an ICMP Type 3 Code 4 packet to force the authoritative server to decrease its UDP segment size for subsequent queries.
  5. E
    Enterprise recursive resolvers initiate all initial lookup queries to root and Top-Level Domain (TLD) authoritative servers over TCP port 53 to prevent cache poisoning attacks.

Cevap

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.

Adım Adım Çözüm

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.

Anahtar Kavram

DNS Transport Protocols and Payload Truncation Mechanics
Bu soruyu puanla

Konular

DNS Lookup and Name Resolution Roles in Enterprise Networks

Bu konudan daha fazla soru