Reverse zone

Mark.Andrews at nominum.com Mark.Andrews at nominum.com
Wed Feb 9 13:49:44 UTC 2000


	The short answer is you have a set of zones:
	0.25.172.in-addr.arpa to 15.25.172.in-addr.arpa
	and
	0.20.172.in-addr.arpa to 15.20.172.in-addr.arpa

	172.25.3.4 would be in 3.25.172.in-addr.arpa
	and
	172.20.0.101 would be in 0.20.172.in-addr.arpa

	The techniques in RFC 2317 are designed for address space
	that cannot otherwise be delegated at a octet boundry.
	Both of these example can be so delegated.

	Mark

> Thanks Daniel,
> Yes, the 172.25.in-addr.arpa was a typo.
> I will have a closer look at rfc2317.  I think this is the first time I heard
> someone say 'bug' related to an rfc ;-)  
> Also, is there not a draft specifying support for unicode character-set in DN
> S?
> Microsoft started with the 'underscore', but i recall someone mentioning comp
> lete
> unicode support..
> Regards,
> Johnny
> 
> At 01:06 PM 2/9/00 +0100, Daniel Roesen wrote:
> > > If I owned 172.0.0.0, I would probably call my reverse zone 172.in-addr.a
> rpa.
> >
> >Correct.
> >
> > > If I owned 172.25.0.0, I would probably call my reverse zone 172.25.in-ad
> dr.arpa.
> >
> >Wrong. 25.172.in-addr.arpa.
> >
> > > If I now have, for example:
> > > host 172.25.3.4, mask 255.255.240.0
> > > and
> > > host 172.20.0.101, mask 255.255.240.0
> > > what would be the proper ???.in-addr.arpa names of these reverse zones fo
> r these hosts.
> >
> >See RFC 2317, but DON'T follow their suggestion to use "/" in the DNS name f
> or
> >the sub-delegation. This is NOT a valid DNS character and will break some
> >resolvers. This suggestions is definately a bug in this RFC.
> >
> >
> >Best regards,
> >Daniel
> 
> 
> 
--
Mark Andrews, Nominum Inc. / Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com



More information about the bind-users mailing list