-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 20-May-2009, at 19:03, John Cole wrote:
For a concrete example: 10.0.0.0/16 is presently handled by a single zone file. 10.1.3.0/24 is DHCP issued 10.1.4.0/24 is DHCP issued
I haven't tested this... but I'm 99% certain that you can simply load them as three separate zones, exactly as you might expect. BIND should recognize that the zone{} statements for 10.1.3/24 and 10.1.4/24 are more-specific than what's in 10.0/16 and act accordingly. Along those same lines, if you happen to have data for either 10.1.3/24 or 10.1.4/24 inside the 10.0/16 zone file, you should get an error.
-----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.11 (Darwin) iEYEARECAAYFAkoUmPAACgkQmFeRJ0tjIxGe4gCgkhfqzbwL9BcT4MtXtqQSMQ08 pmEAn2YNy86QLMcpPd8Rl09d965NskJc =2nvo -----END PGP SIGNATURE----- _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
