Recent problems with Reverse DNS.

Wed Aug 13 20:30:03 UTC 2003

Brett Simpson 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?

The entire 192.168/16 range is reserved by RFC 1918, so a 168.192.in-addr.arpa
reverse zone would be fine.

- Kevin