This is a discussion on Re: Recent problems with Reverse DNS. within the Bind Users forums, part of the DNS and Related Forums category; Brett Simpson wrote: > On Wednesday 13 August 2003 02:38 pm, Kevin Darcy wrote: > > DNS doesn't ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Brett Simpson wrote:
> On Wednesday 13 August 2003 02:38 pm, Kevin Darcy wrote: > > DNS doesn't know from subnets. You could stuff everything into a single > > 168.192.in-addr.arpa zone if you wanted. And if you don't care what the > > reverse lookups resolve to, you could populate it with a single wildcard > > PTR record. Or use $GENERATE to just populate it with generic names. > > I created a 172 reverse zone file with the following entry and it works great. > > *.172.in-addr.arpa. IN PTR generic-reverse-172. 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. - Kevin |