The global/view option
empty-zones-enable yes;
isn't behaving as I expected.
I had expected that it would cause empty "RFC 1918" zones to be created
for those zones for which there were not local zones defined. That is,
if there were no local zones of this type defined, it would create all
the required empty zones. But if 10.in-addr.arpa was defined locally, it
would skip that but define the rest of them.
After looking at my logs, and seeing that I'm leaking RFC 1918 queries,
I see my expectations were wrong.
Is explicitly defining the remaining empty zones the best way to correct
this?
Or maybe add the un-used RFC 1918 zones to our RPZ?
--
--
Do things because you should, not just because you can.
John Thurston 907-465-8591
john.thurs...@alaska.gov
Department of Administration
State of Alaska
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
