From owner-freebsd-questions@freebsd.org Thu Apr 6 18:46:26 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1952D32A73 for ; Thu, 6 Apr 2017 18:46:26 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (mail.geeks.org [IPv6:2001:4980:3333:1::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 885F3836 for ; Thu, 6 Apr 2017 18:46:26 +0000 (UTC) (envelope-from merlyn@geeks.org) Received: from mail.geeks.org (localhost [127.0.0.1]) by after-clamsmtpd.geeks.org (Postfix) with ESMTP id D3CED11023F; Thu, 6 Apr 2017 13:46:17 -0500 (CDT) Received: by mail.geeks.org (Postfix, from userid 1003) id B471F11023E; Thu, 6 Apr 2017 13:46:17 -0500 (CDT) Date: Thu, 6 Apr 2017 13:46:17 -0500 From: Doug McIntyre To: byrnejb@harte-lyne.ca Cc: freebsd-questions@freebsd.org Subject: Re: Bind-9.11 Message-ID: <20170406184617.GA24915@geeks.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Apr 2017 18:46:26 -0000 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.