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

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 18:37 +0200
Message-ID	<mailman.750.1595435831.942.bind-users@lists.isc.org> (permalink)
References	(2 earlier) <d379bee3-e9e5-a9e8-49d9-b92a6bab34a3@suse.de> <295f1ecf-341a-fdc4-96d9-503776a411e7@ripe.net> <2193fa25-9b7c-6a01-ede7-e6d46676cd32@suse.de> <d5f0523a-ed8d-a9cd-f6e1-7487d003ce35@ripe.net> <4bbef49f-f284-d50a-ed3e-a04875f946cd@suse.de>

Show all headers | View raw

On 22.07.20 17:05, Anand Buddhdev wrote:
> On 22/07/2020 16:51, Josef Moellers wrote:
> 
>> 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?
> 
> There is no harm in copying the file into the chroot. It will get rid of
> the warning.

Thanks and ... stay healthy!

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 18:37 +0200

csiph-web