BIND 8.3.3 reverse dns: master zone rejected due to errors

[Kevin Darcy]

Andreas Bachmann wrote:

>Hi all,
>
>I have a problem creating a reverse dns in BIND 8.x
>
>/var/named/named.conf
>
>--------------
>options { 
>	directory "/"; 
>};
>
>zone "." in {
>	type hint;	
>	file "named.root";
>};
>
>zone "te-clan.ch" in {
>	type master;
>	file "db.te-clan.ch";
>};
>
>zone "194.118.217.in-addr.arpa" in {
>	type master;
>	file "db.217.118.194";
>};
>--------------
>
>/var/named/db.217.118.194
>
>--------------
>$ORIGIN 194.118.217.in-addr.arpa.
>40          3600    IN  PTR te-clan.ch.
>            3600    IN  SOA ns1.te-clan.ch. info.te-clan.ch. (
>                            1 10800 3600 86400 86400 )
>            3600    IN  NS  ns1.te-clan.ch.
>            3600    IN  NS  ns2.te-clan.ch.
>--------------
>
>Error
>
>--------------
>[root at te-clan.ch ~] named -d 1 -u bind -g bind -t /var/named named.conf
>[root at te-clan.ch ~] cat named.run
>[...]
>update_zone_info('194.118.217.in-addr.arpa', 1)
>source = db.217.118.194
>purge_zone(194.118.217.in-addr.arpa,1)
>reloading zone
>db_load(db.217.118.194, 194.118.217.in-addr.arpa, 12, Nil, Normal)
>db.217.118.194:6: SOA for "40.194.118.217.in-addr.arpa" not at zone top "194.118.217.in-addr.arpa"
>db.217.118.194: WARNING SOA expire value is less than 7 days (86400)
>Zone "194.118.217.in-addr.arpa" (file db.217.118.194): No default TTL ($TTL <value>) set, using SOA minimum instead
>Zone "194.118.217.in-addr.arpa" (file db.217.118.194): no NS RRs found at zone top
>purge_zone(194.118.217.in-addr.arpa,1)
>master zone "194.118.217.in-addr.arpa" (IN) rejected due to errors (serial 1)
>do_reload: 194.118.217.in-addr.arpa 1 1 1
>purge_zone(194.118.217.in-addr.arpa,1)
>do_reload: matched .
>[...]
>--------------
>
>danks for help!
>
The SOA and NS RRs, since they are given with whitespace as their owner 
name, inherit the previous non-whitespace owner name ("40"). Thus you 
have effectively defined SOA and NS records for 
40.194.118.217.in-addr.arpa, but not for 194.118.217.in-addr.arpa 
itself, which is required.

You can easily fix the problem by giving "@" (= name of the zone) as the 
owner name for the SOA RR. Having done that, stylistically it would then 
be typical to move the "40" RR below the other records, since "apex" RRs 
are usually found at the top of the zone file.

You're wilkomm :-)

                                                                         
                              - Kevin