Large reverse in-addr.arpa delegation

Hulman, Patrick (CCI-Atlanta) Patrick.Hulman at cox.com
Mon Feb 17 18:21:32 UTC 2003


this goes back to my original question. How do i do the delegation for =
these? Sure i could shorten the 10.5.200/21 statement to use a generate =
statement.  But how do i delegate the /15 and the /16 (and yes i've =
looked at D&B v4 p236-7) along w3ith the 21.

patrick
=20




-----Original Message-----
From: David Botham [mailto:dns at botham.net]
Sent: Monday, February 17, 2003 12:36 PM
To: bind-users at isc.org; Hulman, Patrick (CCI-Atlanta)
Subject: RE: Large reverse in-addr.arpa delegation


I would like to correct myself on this email... see below

> -----Original Message-----
> From: David Botham [mailto:dns at botham.net]
> Sent: Wednesday, February 12, 2003 2:38 PM
> To: 'bind-users at isc.org'
> Subject: RE: Large reverse in-addr.arpa delegation
>=20
>=20
>=20
> > -----Original Message-----
> > From: Hulman, Patrick (CCI-Atlanta) [mailto:Patrick.Hulman at cox.com]
> > Sent: Wednesday, February 12, 2003 1:23 PM
> > To: David Botham
> > Cc: bind-users at isc.org
> > Subject: RE: Large reverse in-addr.arpa delegation
> >
> > um. I thought the rfc covered networks with fewer than 256 addresses
ie
> > smaller than a /24.
>=20
> Actually, it addresses delegation of in-addr.arpa zones that correlate
to
> IP networks that are subnetted on Non-Octet Boundaries.  That is to
say
> anything other than:
>=20
> /8, /16, /24 network prefixes...

It (in my opinion) makes no sense to use RFC2317 to delegate as I
indicated above.  As Patrick stated, it only makes sense for the <256
address situations. =20

Multiple delegations are probably the best way to go...  A perl script
is probably the best bet to accomplish the creation of the
delegations...


Dave..



More information about the bind-users mailing list