A network systems engineer is deploying an IPv6-enabled mail gateway. Remote mail servers are failing reverse DNS checks when accepting outbound messages from the gateway's IP address (). The engineer runs the following diagnostic command from a terminal:
text
$ host 2001:db8:85a3::8a2e:370:7334
Host 4.3.3.7.0.7.3.0.e.2.a.8.0.0.0.0.0.0.0.0.3.a.5.8.8.b.d.0.1.0.0.2.ip6.arpa not found: 3(NXDOMAIN)
Which of the following resource records must be configured in the authoritative DNS zone to resolve the NXDOMAIN error?
- A PTR record within the ip6.arpa domain that maps the reverse nibble format of the IPv6 address to the mail gateway's FQDNAnswer
- BAn AAAA record mapping the mail gateway's FQDN to the 2001:db8:85a3::8a2e:370:7334 IPv6 address
- CA PTR record configured to deliver queries across TCP port 25 to match the mail transport protocol
- DAn AAAA record configured to enforce TCP port 53 transport because IPv6 reverse strings exceed standard packet boundaries
Answer
A PTR record within the ip6.arpa domain that maps the reverse nibble format of the IPv6 address to the mail gateway's fully qualified domain name (FQDN).
Reverse DNS lookups resolve IP addresses into hostnames using Pointer (PTR) records. For IPv6, the address is expanded into 32 hexadecimal nibbles, reversed, and appended with .ip6.arpa. Creating a PTR record in this zone allows receiving servers to successfully resolve the mail gateway's IP address.
Step-by-Step Solution
Key Concept
IPv6 Reverse DNS Resolution (PTR Records in ip6.arpa)
Estimated Time:1m 30s