To start with
named[9602]: master/db.192.168.1.32:10: ignoring out-of-zone data (33.1.168.192.in-addr.arpa)
You cannot define the reverse of 192.168.1.33 in a 192.168.1.32 reverse zone file.
Why do you use two
.in-addr.arpa zones? Just use one
1.168.192.in-addr.arpa zone for both the 1 and 33 addresses.
Re: checking zone files
From the named man page
Code:
SEE ALSO
RFC 1033, RFC 1034, RFC 1035, named-checkconf(8),
named-checkzone(8), rndc(8), lwresd(8), named.conf(5),
BIND 9 Administrator Reference Manual.
So there is a
named-checkzone(8) program and man page.
But let me first suggest the following revision of your zone file:
Code:
$TTL 3h
@ IN SOA hydra.wickedbsd.net. root.hydra.wickedbsd.net. (
1 ; Serial
3h ; Refresh after 3 hours
1h ; Retry after 1 hour
1w ; Expire after 1 week
1h ) ; Negative caching TTL of 1 hour
IN NS hydra.wickedbsd.net.
IN MX 10 hydra.wickedbsd.net.
localhost IN A 127.0.0.1
lan IN A 192.168.1.1
hydra IN A 192.168.1.33
www IN A 192.168.1.33
ftp IN A 192.168.1.33
mail IN A 192.168.1.33
wlan IN A 192.168.1.33
;; end of zone
;;
Notice the use of "@" so you don't have to type the "wickedbsd.net." at the end of all host definitions.
My first run of
named-checkzone
Code:
$ named-checkzone wickedbsd.net wickedbsd.net
dns_rdata_fromtext: wickedbsd.net:17: near '192.168,1.33': bad dotted quad
zone wickedbsd.net/IN: loading from master file wickedbsd.net failed: bad dotted quad
I had a comma somewhere in a 192..168.1.33 address. After replacing the comma culprit with the correct period:
Code:
]$ named-checkzone wickedbsd.net wickedbsd.net
zone wickedbsd.net/IN: loaded serial 1
OK
The first wickedbsd.net is the file name, the second one specifies the zone. In this case they just happened to be the same