Jeff Elkins wrote:
A minor note, I'd write db.192 as db.192.168.0, so that if you have another private network it's db.192.168.1 or whatever.On Saturday 27 September 2003 9:10 am, Jeff Elkins wrote:What is a missing ptr?OK, to named.conf I added: zone "192.in-addr.arpa" { type master; file "/etc/bind/db.192"; };
The exact name doesn't matter, but I think it's nice to use numbers all the way down to the subnet you're claiming reverse dns authority for so that you know by glancing at the file name and zone config what network it's a pointer record for.
If you were to include the date in the serial number you could quickly see when you last made zone changes.and /etc/bind/db.192 contains: ; ; BIND reverse data file for 192.168.0.0 ; $TTL 604800 @ IN SOA localhost. root.localhost. ( 1 ; Serial
2003092701 ; Serial in YYYYMMDDSN where "si" is the day's serial increment number
(SN - Sometimes I'll mess up or a second request for changes will come the same day.)
Do you want other computers in the network to look to themselves or the dns server for resolution of the reverse dns zone?604800 ; Refresh 86400 ; Retry 2419200 ; Expire 604800 ) ; Negative Cache TTL ; @ IN NS localhost.
@ IN NS server.elkins
1.0.168.192.in-addr.arpa. IN PTR server.elkins. 2.0.168.192.in-addr.arpa. IN PTR router.elkins. 10.0.168.192.in-addr.arpa. IN PTR kathix.elkins. 20.0.168.192.in-addr.arpa. IN PTR mac.elkins. 30.0.168.192.in-addr.arpa. IN PTR music.elkins. 40.0.168.192.in-addr.arpa. IN PTR buttons.elkins. 50.0.168.192.in-addr.arpa. IN PTR tosh.elkins. 60.0.168.192.in-addr.arpa. IN PTR z.elkins. nslint now reports no errors. Am I on the right track here?
Yep. It's working, right? :)I think it's odd that you had to uninstall/reinstall bind I've not yet had that issue. I'm glad it's working now.
-- Jacob