is this a valid zone file?

Chris Thompson cet1 at cam.ac.uk
Sun Dec 21 16:45:22 UTC 2008


On Dec 21 2008, Jack Tavares wrote:

>Looking at rfc2317
>
>I see the example zone file
>
>$ORIGIN 2.0.192.in-addr.arpa.
>   @       IN      SOA     my-ns.my.domain. hostmaster.my.domain. (...)
>   ;...
>   ;  <<0-127>> /25
>   0/25            NS      ns.A.domain.
>   0/25            NS      some.other.name.server.
>   ;
>   1               CNAME   1.0/25.2.0.192.in-addr.arpa.
>   2               CNAME   2.0/25.2.0.192.in-addr.arpa.
>   3               CNAME   3.0/25.2.0.192.in-addr.arpa.
>   ;
>   ;  <<128-191>> /26
>   128/26          NS      ns.B.domain.
>   128/26          NS      some.other.name.server.too.
>   ;
>   129             CNAME   129.128/26.2.0.192.in-addr.arpa.
>   130             CNAME   130.128/26.2.0.192.in-addr.arpa.
>   131             CNAME   131.128/26.2.0.192.in-addr.arpa.
>   ;
>   ;  <<192-255>> /26
>   192/26          NS      ns.C.domain.
>   192/26          NS      some.other.third.name.server.
>   ;
>   193             CNAME   193.192/26.2.0.192.in-addr.arpa.
>   194             CNAME   194.192/26.2.0.192.in-addr.arpa.
>   195             CNAME   195.192/26.2.0.192.in-addr.arpa.
>
>
>
>That has no NS server defined for the zone, just the ranges of the zone.
>Is that valid?

No. But the "..."s were clearly meant to represent "all the other
usual stuff". After all, the SOA record isn't syntactically valid
either.

-- 
Chris Thompson
Email: cet1 at cam.ac.uk




More information about the bind-users mailing list