Performing a DNS lookup with dig results in this answer:
A.
There is no . after linuserv.example.net in the PTR record in the forward lookup zone file
B.
There is no . after linuserv in the PTR record in the forward lookup zone file
C.
There is no . after linuserv.example.net in the PTR record in the reverse lookup zone file
D.
The . in the NS definition in the reverse lookup zone has to be removed
The Answer Is:
C
This question includes an explanation.
Explanation:
The dig command in the image shows that the reverse DNS lookup for the IP address 192.168.0.1 failed to return the expected hostname linuserv.example.net. Instead, it returned linuserv.example.net.example.net, which indicates that the PTR record in the reverse lookup zone file is missing a dot (.) at the end of the hostname. Without the dot, the hostname is treated as relative to the zone name, which is example.net. Therefore, the correct syntax for the PTR record in the reverse lookup zone file should be:
1.168.192.in-addr.arpa. IN PTR linuserv.example.net.
The dot at the end of the hostname makes it absolute, meaning it does not append the zone name to it. This way, the reverse DNS lookup will return the correct hostname for the IP address123 References:
Reverse DNS Lookup - WhatIsMyIP.com®
DNS PTR Records - DNSimple Help
How to Configure Reverse DNS for BIND in WHM - cPanel Knowledge Base - cPanel Documentation
What is a DNS PTR Record? PTR Record Syntax & Examples - PowerDMARC
202-450 PDF/Engine
Printable Format
Value of Money
100% Pass Assurance
Verified Answers
Researched by Industry Experts
Based on Real Exams Scenarios
100% Real Questions
Get 65% Discount on All Products,
Use Coupon: "ac4s65"