bind 9.1.0 zone errors

[Mark.Andrews at nominum.com]

> 
> I am trying to upgrade from 8.x to 9.1.0 but I am getting the following error
> with all my zone files:
>   Feb 17 12:54:16 lookout named[17958]: dns_master_load: pz/127.0.0:11: not a
> t top of zone
>   Feb 17 12:54:16 lookout named[17958]: dns_zone_load: zone 0.0.127.in-addr.a
> rpa/IN: loading master file pz/127.0.0: not at top of zone
> 
> line 11 is the first PTR record:
> 
> ========== my pz/127.0.0.0 file ===============
> $ORIGIN 0.0.127.in-addr.arpa

	Which is interpeted as:

	$ORIGIN 0.0.127.in-addr.arpa.0.0.127.in-addr.arpa.

	Hence the SOA record was not at the top of zone.

	Mark


> $TTL 86400      ; 1 day
> @               IN      SOA     ns.gus.ca. root.gus.ca. (
>                                 1               ; Serial
>                                 28800           ; Refresh
>                                 7200            ; Retry
>                                 604800          ; Expire
>                                 86400)          ; Minimum TTL
>                      IN NS      ns.gus.ca.
> 0.0.0.127.in-addr.arpa                    IN PTR     loopback.
> 1.0.0.127.in-addr.arpa                    IN PTR     localhost.
> ==========                      ===============
> 
> I am getting the same thing with all my zones though, this is just the simple
> st
> one.
> 
> ========== my named.conf file ===============
> options {
>         directory "/var/named"; 
> };                     
>                      
> zone "." {
>         type hint;
>         file "root.hints";
> };
> 
> zone "0.0.127.in-addr.arpa" {
>         type master;
>         file "pz/127.0.0";
> };
> 
> ...
> ==========                    ===============
> 
> 
> thanks for the help. 
> 
> also I really think the bind-9 documentation should have more example zone
> files.
> 
> cheers, Angus.
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com