As far as I know it is good to include two more zone files in every nameserver. I believe they do not break anything, although I get: # /etc/init.d/named start * Could not get dependency info for "named"! * Could not get dependency info for "named"! * Starting chrooted named... [ ok ] # Which actually I do not know what means. Reproducible: Always Steps to Reproduce: 1. 2. 3. --- /dev/null 1970-01-01 01:00:00.000000000 +0100 +++ /etc/bind/pri/0 2003-07-02 12:27:33.000000000 +0200 @@ -0,0 +1,11 @@ +; +; BIND reverse data file for broadcast zone +; +$TTL 604800 +0.0.0.in-addr.arpa. IN SOA localhost. root.localhost. ( + 1 ; Serial + 604800 ; Refresh + 86400 ; Retry + 2419200 ; Expire + 604800 ) ; Negative Cache TTL +0.0.0.in-addr.arpa. IN NS localhost. --- /dev/null 1970-01-01 01:00:00.000000000 +0100 +++ /etc/bind/pri/255 2003-07-02 12:27:52.000000000 +0200 @@ -0,0 +1,12 @@ +; +; BIND reverse data file for broadcast zone +; +$TTL 604800 +0.0.255.in-addr.arpa. IN SOA localhost. root.localhost. ( + 1 ; Serial + 604800 ; Refresh + 86400 ; Retry + 2419200 ; Expire + 604800 ) ; Negative Cache TTL +; +0.0.255.in-addr.arpa. IN NS localhost. --- /etc/bind/named.conf.ori 2003-07-02 12:21:36.000000000 +0200 +++ /etc/bind/named.conf 2003-07-02 12:23:40.000000000 +0200 @@ -40,3 +40,20 @@ allow-update { none; }; notify no; }; + +zone "0.in-addr.arpa" { + type master; + file "pri/0"; + allow-query { any; }; + allow-update { none; }; + notify no; +}; + +zone "255.in-addr.arpa" { + type master; + file "pri/255"; + allow-query { any; }; + notify no; + allow-update { none; }; +}; +
done
