Recent problems with Reverse DNS.

Barry Margolin barry.margolin at level3.com
Wed Aug 13 20:32:24 UTC 2003


In article <bhe6rs$5lg$1 at sf1.isc.org>,
Brett Simpson  <simpsonb at hillsboroughcounty.org> wrote:
>On Wednesday 13 August 2003 04:02 pm, Kevin Darcy wrote:
>> Well, technically RFC 1918 only reserved 172.16/12. You could end up
>> accidentally blinding yourself to legitimate reverse lookups if you define
>> 172.in-addr.arpa.
>
>Does that also apply to using 168.192.in-addr.arpa?

No, RFC 1918 reserves all 192.168.x.x and 10.x.x.x addresses, so each of
these ranges can each be handled in a single reverse zone.  But in the
172.x.x.x range, only 172.16.x.x through 172.31.x.x are reserved.  So
instead of one 172.in-addr.arpa zone, you should create 16 zones for
16.172.in-addr.arpa through 31.172.in-addr.arpa.

-- 
Barry Margolin, barry.margolin at level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list