Performing a DNS lookup with dig results in this answer: ;; question SECTION:
;5.123.168.192.in-addr.arpa. IN PTR ;; ANSWER SECTION: 5.123.168.192.in-addr.arpa.
600 IN PTR linuserv.example.net.123.168.192.in-addr.arpa. ;;AUTHORITY SECTION:
123.168.192.in-addr.arpa. 600 IN NS linuserv.example.net. ;; ADDITIONAL SECTION:
linuserv.example.net. 600 IN A 192.168.123.5 What might be wrong in the zone definition?
A.
The “.” in the NS definition in reverse lookup zone has to be removed.
B.
There’s no “.” after linuserv.example.net in the PTR record in the reverse lookup zone
file.
C.
Nothing. All seems to be good.
D.
There’s no “.” after linuserv.example.net in the PTR record in the forward lookup zone
file.
E.
There’s no “.” after linuserv in the PTR record in the forward lookup zone file.
B. is correct
Explanation:
The output was generated by the following dig:
Dig PTR 5.123.168.192.in-addr.arpa
In the answer section the PTR entry has the default domain added to the actual domain name,
indicating that the PTR record in the reverse lookup zone file is specified incorrectly.