1.7.3 - trusted-keys-file location

Wouter Wijngaards wouter at nlnetlabs.nl
Fri Jul 27 09:26:59 UTC 2018


Fixed the documentation in the man page to more clearly state that
chroot is enabled by default. In addition, it lists the default setting
for it as well.  If you are using man pages online, that gets updated
when we release a new version, the man page source is already available
in the source code repository.

Best regards, Wouter

On 26/07/18 17:34, ѽ҉ᶬḳ℠ via Unbound-users wrote:
> That is not very clear (to me) from the online documentation:
>> The default is "/usr/local/etc/unbound". If you give "" no chroot is
> performed. <
> It implies a default directory but It does not expressively state that
> chroot is enabled by default.
>> Best regards, Wouter
>>> Since the authoritative server being Bind 9.13.0 I thought it would make
>>> sense to utilize its zone file straight away for unbound as >
>>> trusted-keys-file: "/var/named/mail.db" <. However, unbound is reporting
>>> /etc/unbound/var/named/mail.db: No such file or directory
>>> [1532614243] unbound-checkconf[2467:0] fatal error: trusted-keys-file:
>>> "/var/named/mail.db" does not exist in chrootdir /etc/unbound
>>> There is no chroot directive in the unbound conf however...

More information about the Unbound-users mailing list