Question about RFC-2317

Clenna Lumina savagebeaste at
Thu Jan 4 10:42:10 UTC 2007

I was reading about RFC-2317
(, found via google... is
there a newer one?) 

While I feel I have grasped a lot about DNS/Bind the past
couple months (enough to setup zones for my LAN and started
to manage a couple external domains I've since had deligated
to me), I can't see understand one part in this RFC document.

On page 2 (and 3) it shwos a nice example of how to partition
a class C address space into chunks (in that case, starting
from, /25, /26, and /26

I understand that CNAMing in the parent zone is needed,
acccording to this RFC.

What I can't seem to figure out for the life of me is *why*
this is needed?

(Example parent zone from RFC-2317)
   @       IN      SOA (...)
   ;  <<0-127>> /25
   0/25            NS      ns.A.domain.
   0/25            NS
   1               CNAME   1.0/
   2               CNAME   2.0/
   3               CNAME   3.0/
   ;  <<128-191>> /26
   128/26          NS      ns.B.domain.
   128/26          NS
   129             CNAME   129.128/
   130             CNAME   130.128/
   131             CNAME   131.128/
   ;  <<192-255>> /26
   192/26          NS      ns.C.domain.
   192/26          NS
   193             CNAME   193.192/
   194             CNAME   194.192/
   195             CNAME   195.192/

It doesn't seem to make sense with the NS entries pointing to
the name servers that those chunks (/lengths) are being
deligated to. Wouldn't each respective NS server(s) handle it
instead. The CNAME is just an alias, right, so is it needed
here? As a fall back messure? Unless I've missed something,
the RFC doesn't seem to expalin that.


Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 

More information about the bind-users mailing list