/etc/bind.keys in a chrooted environment
Josef Moellers
jmoellers at suse.de
Wed Jul 22 13:30:28 UTC 2020
On 22.07.20 15:28, Anand Buddhdev wrote:
> On 22/07/2020 15:06, Josef Moellers wrote:
>
> Hi Josef,
>
>> named complains about the missing file /etc/bind.keys if run chrooted:
>> unable to open '/etc/bind.keys' using built-in keys
>>
>> What is the preferred way around this? Add "/etc/bind-keys" to
>> NAMED_CONF_INCLUDE_FILES?
>
> Or just ignore the warning, and let BIND use its built-in keys.
If /etc/bind.keys contains some additional keys, this will not work ;-)
Josef
--
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
More information about the bind-users
mailing list