Large reverse in-addr.arpa delegation (Revisited)

[Hulman, Patrick (CCI-Atlanta)]

yup thanks David.  I had just finished getting this to work in my lab =
when i saw your email.

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



I have gone back to your original email...
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of Hulman, Patrick (CCI-Atlanta)
> Sent: Wednesday, February 12, 2003 11:35 AM
> To: bind-users at isc.org
> Subject: Large reverse in-addr.arpa delegation
>=20
> I'm trying to delegate large chunks of ip space.  I'm using a 10
network =3D
> where I need to delegate three /16 and a /21 to different servers. In
=3D
> this case i want to delegate 10.2.x.x/15 to ns1.foo.com and
ns2.foo.com, =3D
> 10.4.x.x to ns1.foo2.com ns2.foo2.com and 10.5.200.0/21 to
ns1.foo3.com =3D
> and ns2.foo3.com


10.2.0.0/15 could be done like this:

2.10.in-addr.arap	IN	NS	ns1.foo.com.
2.10.in-addr.arap	IN	NS	ns2.foo.com.
3.10.in-addr.arap	IN	NS	ns1.foo.com.
3.10.in-addr.arap	IN	NS	ns2.foo.com.

These two delegations cover all the addresses in the requested range,
that is 10.2.0.0 to 10.3.0.0.




This would work for the 10.4.0.0 section (note that I assume this is
*not* a /15).
4.10.in-addr.arap	IN	NS	ns1.foo2.com.
4.10.in-addr.arap	IN	NS	ns2.foo2.com.



For the 10.5.200.0/21, these would work:

200.5.10.in-addr.arpa	IN	NS	ns1.foo3.com.
200.5.10.in-addr.arpa	IN	NS	ns2.foo3.com.
201.5.10.in-addr.arpa	IN	NS	ns1.foo3.com.
201.5.10.in-addr.arpa	IN	NS	ns2.foo3.com.
202.5.10.in-addr.arpa	IN	NS	ns1.foo3.com.
202.5.10.in-addr.arpa	IN	NS	ns2.foo3.com.
203.5.10.in-addr.arpa	IN	NS	ns1.foo3.com.
203.5.10.in-addr.arpa	IN	NS	ns2.foo3.com.
204.5.10.in-addr.arpa	IN	NS	ns1.foo3.com.
204.5.10.in-addr.arpa	IN	NS	ns2.foo3.com.
205.5.10.in-addr.arpa	IN	NS	ns1.foo3.com.
205.5.10.in-addr.arpa	IN	NS	ns2.foo3.com.
206.5.10.in-addr.arpa	IN	NS	ns1.foo3.com.
206.5.10.in-addr.arpa	IN	NS	ns2.foo3.com.
207.5.10.in-addr.arpa	IN	NS	ns1.foo3.com.
207.5.10.in-addr.arpa	IN	NS	ns2.foo3.com.


Does that help?

Dave...


>=20
> My question is how would the 10.in-addr.arpa look
>=20
> would it be
> 0.2.10.in-addr.arpa.	86400	IN	NS	ns1.foo.com.
> 0.2.10.in-addr.arpa.	86400	IN	NS	ns2.foo.com.
> 1.2.10.in-addr.arpa.	86400 	IN	NS	ns1.foo.com.
> 1.2.10.in-addr.arpa.	86400	IN	NS	ns2.foo.com.
> .
> .
> .
> 254.3.10.in-addr.arpa.	86400	IN	NS	ns1.foo.com.
> 254.3.10.in-addr.arpa.	86400	IN	NS	ns2.foo.com.
> 255.3.10.in-addr.arpa.	86400	IN	NS	ns1.foo.com.
> 255.3.10.in-addr.arpa.	86400	IN	NS	ns2.foo.com.
>=20
>=20
> 0.4.10.in-addr.arpa.	86400	IN	NS	ns1.foo2.com.
> 0.4.10.in-addr.arpa.	86400	IN	NS	ns2.foo2.com.
> 1.4.10.in-addr.arpa.	86400 	IN	NS	ns1.foo2.com.
> 1.4.10.in-addr.arpa.	86400	IN	NS	ns2.foo2.com.
> .
> .
> .
> 254.4.10.in-addr.arpa.	86400	IN	NS	ns1.foo2.com.
> 254.4.10.in-addr.arpa.	86400	IN	NS	ns2.foo2.com.
> 255.4.10.in-addr.arpa.	86400	IN	NS	ns1.foo2.com.
> 255.4.10.in-addr.arpa.	86400	IN	NS	ns2.foo2.com.

No, this is not necessary unless you are delegating to different name
servers.

>=20
> 200.5.10.in-addr.arpa.	86400	IN	NS	ns1.foo3.com.
> 200.5.10.in-addr.arpa.	86400	IN	NS	ns2.foo3.com.
> 201.5.10.in-addr.arpa.	86400 IN	NS	ns1.foo3.com.
> 201.5.10.in-addr.arpa.	86400	IN	NS	ns2.foo3.com.
> .
> .
> .
> 207.5.10.in-addr.arpa.	86400	IN	NS	ns1.foo3.com.
> 207.5.10.in-addr.arpa.	86400	IN	NS	ns2.foo3.com.
> 207.5.10.in-addr.arpa.	86400	IN	NS	ns1.foo3.com.
> 207.5.10.in-addr.arpa.	86400	IN	NS	ns2.foo3.com.

This is correct for the 10.5.200.0/21, just as you have shown it below.



>   or=3D20
>=20
> 2.10.in-addr.arpa.	86400	IN	NS	ns1.foo.com.
> 2.10.in-addr.arpa.	86400	IN	NS	ns2.foo.com.
> 3.10.in-addr.arpa.	86400 IN	NS	ns1.foo.com.
> 3.10.in-addr.arpa.	86400	IN	NS	ns2.foo.com.


Yup, this covers the 10.2.0.0/15.



> 4.10.in-addr.arpa.	86400 	IN	NS	ns1.foo2.com.
> 4.10.in-addr.arpa.	86400	IN	NS	ns2.foo2.com.

And this covers the 10.4.0.0/16.



>=20
> 200.5.10.in-addr.arpa.	86400	IN	NS	ns1.foo3.com.
> 200.5.10.in-addr.arpa.	86400	IN	NS	ns2.foo3.com.
> 201.5.10.in-addr.arpa.	86400 	IN	NS	ns1.foo3.com.
> 201.5.10.in-addr.arpa.	86400	IN	NS	ns2.foo3.com.
> .
> .
> .
> 207.5.10.in-addr.arpa.	86400	IN	NS	ns1.foo3.com.
> 207.5.10.in-addr.arpa.	86400	IN	NS	ns2.foo3.com.
> 207.5.10.in-addr.arpa.	86400	IN	NS	ns1.foo3.com.
> 207.5.10.in-addr.arpa.	86400	IN	NS	ns2.foo3.com.

And yes, this covers the 10.5.200.0/21.


Hope this helps.  The perl script to automate the generation of these
delegations should be fairly straight forward.


Dave...

>=20
> or is it something else entirely
>=20
>=20
> patrick
>=20
>=20