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

[Carl Byington]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 2015-08-12 at 11:26 +1000, blueonyxuser at gmail.com wrote:
> So essentially I need to cover 192.168.20.x through to 192.168.254.x
> within the BO but not the whole 192.168/16 - which makes it difficult
> I think.

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?


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)

iEYEARECAAYFAlXKrq0ACgkQL6j7milTFsG+AACfdPEZUCwrs5NxU1byGgzUvXsm
XPcAn2P/jHz5nZUSZD4RyEt3b2T3msiG
=eI6j
-----END PGP SIGNATURE-----