Re: Recent problems with Reverse DNS.

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.

> On the other hand, it shouldn't be hard (I know because I've done it in the
> past) to just collect all of the data from your forward zones and just
> massage it all into PTR records with which to populate your reverse
> zone(s). Then you actually have *real* reverse lookups, which is convenient
> for things like network troubleshooting (think ping or traceroute),
> logging, etc.

I agree. At this time I don't have a forward entry for every internal IP
address. I would consider using Dynamic DNS to facilitate this but the DHCP
server is not under my control. I think it's running a proprietary DHCP
server that doesn't work with Bind.

Thanks for your help.

Brett