bind911 fatal error with LMDB and allow-new-zones in chrooted environment

[Mathieu Arnold]

Hi,

On Mon, Jun 11, 2018 at 02:43:41PM +0200, Ciernik Tomas wrote:
> Hello,
> 
> I am experiencing fatal error during start after upgrading bind99 to
> bind911.
> 
> I used soon-to-be-EOL bind99 in chrooted environment with support for
> dynamically adding of zones. With upgrade to bind911 I decided to add
> support for LMDB, too.
> 
> With this configuration (chroot, lmdb support, allow-new-zones in
> named.conf) bind refuses to start with error
> 
> mdb_env_open of '_default.nzd' failed: No such file or directory
> 
> although bind user has full ACL for working directory.
> 
> Did I overlook something? Problem was resolved by disabling support for
> LMDB, but it will be nice to have this feature included.
> 
> Maybe interesting point - new file _default.nzd-lock is added into
> working directory, his owner is root and ACLs are 600.

Could you please open a PR about this, and provide a precise way to
reproduce the problem (like what exact lines to add to the configuration
file, and so on.)

-- 
Mathieu Arnold
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20180612/beeee336/attachment.sig>