[BlueOnyx:18159] Re: Changes in DNS logs since recent updates

[blueonyxuser at gmail.com]

> Not really.
> 
> Create the 168.192.in-addr.arpa zone following directions from Michael,
> 
> then add records like:
> 
> 5.0   ptr  some.name.
> 6.0   ptr  another.name.
> ;
> 5.20  ptr  some.vpn.name.
> 6.20  ptr  another.vpn.name.
> ;
> 5.254 ptr  more.names.
> 6.254 ptr  yet.more.names.
> 
> You don't need to fully populate all 64K ptr records. The existence of the
168.192.in-
> addr.arpa zone will prevent all of those queries from reaching the .arpa
servers.
> 
> Alternatively, you *could* create 256 separate /24 zones (0.168.192.in-
addr.arpa
> thru 255.168.192.in-addr.arpa), but that is a lot more work.
> 
> You might also want to create the 10.in-addr.arpa zone, and the 16 thru
31.172.in-
> addr.arpa zones. Do you have any clients using your dns server that might
do
> reverse lookups in those address ranges?

Thanks to both you and Michael I think I now have this worked out.

I ended up creating;

	192.168.16.0/255.255.240.0	Reverse
	192.168.128.0/255.255.128.0	Reverse	
	192.168.64.0/255.255.192.0	Reverse	
	192.168.32.0/255.255.224.0	Reverse	

... which covers all the ranges I need in 4 easy steps.

I just assigned them to an existing domain as they won't be used by anyone
who is not already using a username from that domain.

Learning every day ( well if it is right ) :-)

Tony