Groups > comp.protocols.dns.bind > #16004

Re: /etc/bind.keys in a chrooted environment

From	Josef Moellers <jmoellers@suse.de>
Newsgroups	comp.protocols.dns.bind
Subject	Re: /etc/bind.keys in a chrooted environment
Date	2020-07-22 16:51 +0200
Message-ID	<mailman.746.1595429488.942.bind-users@lists.isc.org> (permalink)
References	<0e03752f-9ce1-ff80-ee4b-14416e94cbde@suse.de> <41683619-f25c-29ff-f1b8-78bc8625858f@ripe.net> <d379bee3-e9e5-a9e8-49d9-b92a6bab34a3@suse.de> <295f1ecf-341a-fdc4-96d9-503776a411e7@ripe.net> <2193fa25-9b7c-6a01-ede7-e6d46676cd32@suse.de>

Show all headers | View raw

On 22.07.20 16:41, Anand Buddhdev wrote:
> On 22/07/2020 15:30, Josef Moellers wrote:
> 
>>> 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 ;-)
> 
> Sure, but what additional keys do you expect this file to contain? Are
> you serving an alternate signed root zone?

I'm not really sure what the partner wants to add, I have the slight
feeling that the remark about manually added keys was made by a third
person assuming ...

It turns out that it is mainly the warning the partner is irritade about.

So, let me put the question the other way round: what would happen if we
*always* copied /etc/bind.keys to the chroot environment? If there would
be no harm, I could easily add that to eg /etc/init.d/named or the
systemd service file. But the question now is: does it do any harm?

Thanks,

Josef
-- 
SUSE Software Solutions Germany GmbH
Maxfeldstr. 5
90409 Nürnberg
Germany

(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer

Back to comp.protocols.dns.bind | Previous | Next | Find similar

Thread

Re: /etc/bind.keys in a chrooted environment Josef Moellers <jmoellers@suse.de> - 2020-07-22 16:51 +0200

csiph-web