Doug McIntyre merlyn at
Thu Apr 6 18:46:26 UTC 2017

On Thu, Apr 06, 2017 at 09:09:49AM -0400, James B. Byrne via freebsd-questions wrote:
> I have set up a Bind-9.11 service (inside a jail).  In doing so I
> noted that the default named.conf file provided contains no less than
> 161 pre-defined zones that all point to:
>     /usr/local/etc/namedb/master/empty.db
> So, what happened to the 'empty-zones-enable' and 'disable-empty-zone'
> options?  Why are these zones explicitly defined?

Those are "relatively new" features to BIND. BIND used to not do that,
and it used to be a issue with users looking up private IP space reverses
all that time against your servers.

The FreeBSD setup can probably be adjusted and modified to use the built
in BIND features now. But it was useful in the past.

More information about the freebsd-questions mailing list