rDNS Failing with NXDOMAIN Error

PTR records are not resolving. When using the following command:

set service dns forwarding authoritative-domain 0.2.168.192.in-addr.arpa records ptr 36 target mydomain.local

I then commit, save and running:

nslookup 192.168.2.36

Produces a NXDOMAIN error.

Try this instead:

set service dns forwarding authoritative-domain 2.168.192.in-addr.arpa records ptr 36 target mydomain.local

That is the zone is “2.168.192.in-addr.arpa” who then contains “PTR 36 mydomain.local” and is resolved by “nslookup 192.168.2.36” or “dig 36.2.168.192.in-addr.arpa”.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.