Performing a DNS lookup with dig results in this answer: What might be wrong in the zone definition?

Performing a DNS lookup with dig results in this answer: What might be wrong in the zone definition?

 

Performing a DNS lookup with dig results in this answer: What might be wrong in the zone definition?

 

A.
Nothing. All seems to be good.

B.
There’s no "." after linuserv.example.net in the PTR record in the forward lookup zone file.

C.
There’s no "." after linuserv in the PTR record in the forward lookup zone file.

D.
There’s no "." after linuserv.example.net in the PTR record in the reverse lookup zone file.

E.
The "." in the NS definition in reverse lookup zone has to be removed.



Leave a Reply 3

Your email address will not be published. Required fields are marked *


stephen

stephen

The lookup results in WHAT answer?

seenagape

seenagape

Correct answer is

yaim

yaim

Here’s the results

;; 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