Classless in-addr.arpa delegation

[Kevin Darcy]

Actually, the owner of the /16 zone would need to delegate any /24 subzones.


- Kevin

Tim Maestas wrote:

>         If you are delegating a whole class C, RFC2317 does
>         not need to be used.  Only when you are delegating
>         on non-octet boundries, ie less than a /24 do you need
>         to do classless in-addr.arpa delegation.
>
>         If you have been delegated 16.172.in-addr.arpa, then in the
>         zone file for that zone, you can have:
>
>         5.16.172.in-addr.arpa.  IN      NS other.name.server.here.
>                                 IN      NS second.name.server.here.
>         This would delegate 172.16.5.0/24 to the 2 ns's listed.
>
> -Tim
>
> On Fri, 5 Jan 2001, Robert Stoll wrote:
>
> >
> > Hi everyone,
> >    I'm looking for the best way to delegate part of an in-addr.arpa domain
> > to another name server.  Let me paint the picture for you:
> >
> >    We have a CIDR block assigned from our ISP, for the sake of this message,
> > let's say its 172.16.0.0/18, which gives me 64 class C nets, 172.16.0.0 -
> > 172.16.63.0.  I want a branch office to have complete control over one of
> > the class C address spaces.  Setting up the forward delegation is easy, but
> > what is the best way of delegating the reverse?  I've read through RFC 2317,
> > and I agree that it is pretty ugly, but since it is a couple of years old
> > I'm hoping there is a better way of doing it.
> >
> >   I'm sure I'm not the only person who has had to do this, so I'm hoping one
> > of you can help me out.  Sample zone files would be appreciated. :-)
> >
> >
> > Thanks much.
> >
> > Bob...
> >
> >
> >
> >