A network administrator is troubleshooting an authentication service failure where an internal enterprise application requires reverse DNS verification before granting access to incoming clients. The administrator runs the command `dig -x 192.168.50.25` and receives the following output:
text
;; QUESTION SECTION:
;25.50.168.192.in-addr.arpa. IN PTR
;; AUTHORITY SECTION:
50.168.192.in-addr.arpa. 3600 IN SOA ns1.corp.internal. hostmaster.corp.internal. 2026072701 7200 3600 1209600 3600
Which resource record configuration must be added to the authoritative zone to resolve the hostname verification failure?
- A PTR record mapping 25.50.168.192.in-addr.arpa. to the client host's fully qualified domain nameCevap
- BAn A record mapping 25.50.168.192.in-addr.arpa. directly to 192.168.50.25 within the reverse lookup zone
- CA CNAME record alias configured to redirect reverse lookup queries over TCP port 53
- DAn SRV record in the forward zone specifying UDP port 53 for reverse resolution services
Cevap
A PTR record mapping 25.50.168.192.in-addr.arpa. to the host's fully qualified domain name must be created in the reverse lookup zone.
The output of `dig -x` demonstrates a query for a PTR record (`25.50.168.192.in-addr.arpa. IN PTR`). The absence of an ANSWER section confirms that no PTR record currently exists for IP 192.168.50.25. Adding a valid PTR record mapping the reverse address to the host's FQDN in the authoritative zone resolves the reverse lookup request.
Adım Adım Çözüm
Anahtar Kavram
DNS Reverse Lookup and PTR Record Configuration