LPI
117-201 · Question #32
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
The correct answer is D. There's no "." after linuserv.example.net in the PTR record in the reverse lookup zone file.. See the full explanation below for the reasoning.
Question
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?
Options
- ANothing. All seems to be good.
- BThere's no "." after linuserv.example.net in the PTR record in the forward lookup zone file.
- CThere's no "." after linuserv in the PTR record in the forward lookup zone file.
- DThere's no "." after linuserv.example.net in the PTR record in the reverse lookup zone file.
- EThe "." in the NS definition in reverse lookup zone has to be removed.
How the community answered
(30 responses)- A10% (3)
- C3% (1)
- D80% (24)
- E7% (2)
Community Discussion
No community discussion yet for this question.