Reverse zone with subnet larger than Class C

Mark Andrews Mark_Andrews at isc.org
Thu Mar 2 02:35:09 UTC 2006


> In article <du3k5h$m36$1 at sf1.isc.org>, Mark_Andrews at isc.org says...
> > 
> > > Hi,
> > > 
> > > I trying to add some more reverse zones in bind 9.3.1. 
> > > 
> > > The problem is that I would like to add zones like 192.168.0.0/22,
> > > 192.168.4.0/22 and so on.
> > > 
> > > Is that possible with BIND?
> > > 
> > > I've tried several configs:
> > > 
> > > named.conf:
> > > 
> > > zone "0-22.168.192.IN-ADDR.ARPA" in {
> > > 	type master;
> > > 	file "rev/192.168.0-22.rev.db";
> > > };
> > > 
> > > or
> > > 
> > > zone "0/22.168.192.IN-ADDR.ARPA" in {
> > > 	type master;
> > > 	file "rev/192.168.0-22.rev.db";
> > > };
> > > 
> > > But none of those worked.
> > > 
> > > My reverse zone file works because if I only add it as Class C it
> > > works.
> > > 
> > > Anyone know how to do it if possible?
> > > 
> > > Regards,
> > > Torkel
> > 
> > 	Just delegate the sets of 4 zones.
> 
> How?

	0.168.192.IN-ADDR.ARPA NS NS1.site1.example.net.
	0.168.192.IN-ADDR.ARPA NS NS2.site1.example.net.
	1.168.192.IN-ADDR.ARPA NS NS1.site1.example.net.
	1.168.192.IN-ADDR.ARPA NS NS2.site1.example.net.
	2.168.192.IN-ADDR.ARPA NS NS1.site1.example.net.
	2.168.192.IN-ADDR.ARPA NS NS2.site1.example.net.
	3.168.192.IN-ADDR.ARPA NS NS1.site1.example.net.
	3.168.192.IN-ADDR.ARPA NS NS2.site1.example.net.

	4.168.192.IN-ADDR.ARPA NS NS1.site2.example.net.
	4.168.192.IN-ADDR.ARPA NS NS2.site2.example.net.
	5.168.192.IN-ADDR.ARPA NS NS1.site2.example.net.
	5.168.192.IN-ADDR.ARPA NS NS2.site2.example.net.
	6.168.192.IN-ADDR.ARPA NS NS1.site2.example.net.
	6.168.192.IN-ADDR.ARPA NS NS2.site2.example.net.
	7.168.192.IN-ADDR.ARPA NS NS1.site2.example.net.
	7.168.192.IN-ADDR.ARPA NS NS2.site2.example.net.
 
> I only got 1 domain so the domain will still be "test.com". I just want 
> more reverse zones.
> 
> So how to delegate reverse zones like 192.168.0.0/22, 192.168.4.0/22 .. 
> 192.168.44.0/22
> 
> But I was hoping that I would be able to add 12 /22 zones rather than 48 
> Class C reverse zones.. 
> 
> Regards,
> Torkel

	IN-ADDR.ARPA is octet aligned and it followed the original
	address assignment rules which were also octet aligned.
	Modern address assignemnt is bit aligned.

	We looked at doing bit aligned delegations for IPv6 and
	gave them up as a bad idea.  IPv6 uses nibble alignment
	under IP6.ARPA.  While address assignment for IPv6 is bit
	aligned I suspect that most assignments will end up being
	nibble aligned.  For the off nibble assignments there will
	be multiple sets of delegations.

	In reality you have most probably spent more time trying
	to find a alternate mechanism than it would have cost you
	to just do it.  In addition to that you won't have do deal
	with a common problem of /16 delegations which is forgetting
	to reverse the last two octets.

	Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org



More information about the bind-users mailing list