A network administrator is attempting to perform a manual zone transfer from an authoritative internal DNS server at for the domain . While standard host resolution queries function normally, the zone transfer fails as shown in the command output below:
text
$ dig @192.168.10.5 internal.corp.com AXFR
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached
Which of the following firewall configuration changes is required to resolve this DNS operational failure?
- Allow inbound traffic to destination TCP port 53 on the DNS server.Answer
- BConfigure the client query to enforce UDP port 53 with the +notcp flag, as zone transfers are restricted to connectionless transport.
- CChange the query record type from AXFR to CNAME to retrieve the complete domain zone structure.
- DPermit inbound traffic to destination UDP port 5353 to enable zone transfer replication across local subnets.
Answer
Allow inbound traffic to destination TCP port 53 on the DNS server.
DNS primary/secondary replication and manual zone transfers utilize the AXFR query type. Unlike standard lookup queries that run over UDP port 53, zone transfers require TCP port 53 to handle bulk data delivery securely and reliably without packet truncation. Opening TCP port 53 allows the client connection to establish successfully.
Step-by-Step Solution
Key Concept
DNS Transport Protocols (UDP vs TCP Port 53)
Estimated Time:2m 0s