We use h2n to generate our db files, but NOT to generate named.conf. We recently add the network 10.160.0.0:255.240.0.0 to h2n, which then generated db.10.160, db.10.161, etc.
All of these 16-bit networks will reside in the same zone. Is there a way to either get h2n to generate one db for the entire range, or to configure named.conf to use all 16 db files in one zone statement? _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users