Reverse Zone

Question

I thought I had DNS working but now dig -x 192.168.1.112 does not report a PTR record.
Primary Zone jamestownpress.net.
A Record:
Machine Name: server Value: 192.168.1.112
Reverse Zone
Name: 1.168.192.in-addr.arpa. Type: Reverse Zone Value: -
192.168.1.112 Reverse Mapping server.jamestownpress.net
When I select the reverse zone It reports that the Nameserver Host Name is:
192.168.1.112.jamestownpress.net.
That doesn't seem right.
And how does server admin come up with the automatically created reverse zone name 1.168.192.

Answer 1

That doesn't seem right.
Do forward and reverse DNS translations (the dig and +dig -x+ commands) requests work?
I'd tend to have the DNS name server host name set in the reverse zone. Server Admin can unfortunately be a little fussy when you're first setting stuff up the zones, and if you miss a prompt or a definition, then this stuff can be a little wonky. If you have server.jamestownpress.net set up as the forward name of your DNS server for your zone, then specify it in your reverse zone.
And how does server admin come up with the automatically created reverse zone name 1.168.192.
That's based on the subnet mask. You probably have 192.168.1.0/24, sharing that IP address usage with most every coffee shop and home network on the planet.
Apropos of coffee shops and home networks and the eventual use of VPNs and the resulting IP subnet routing conflicts when VPNs are eventually needed, it can be best to move your network out of 192.168.0.0/16 before you get too far along to easily change your address block.