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

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

From	tale <d.lawrence@salesforce.com>
Newsgroups	comp.protocols.dns.bind
Subject	Re: /etc/bind.keys in a chrooted environment
Date	2020-07-22 11:34 -0400
Message-ID	<mailman.748.1595432060.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> <CAGrdBBvEZdJ1XHOXutxqMTE1cnGXhhyiN5sa=jy=5mzt5VS07A@mail.gmail.com>

Show all headers | View raw

On Wed, Jul 22, 2020 at 11:05 AM Anand Buddhdev <anandb@ripe.net> wrote:
> There is no harm in copying the file into the chroot. It will get rid of
> the warning.

With the caveat that you have to be sure that if you keep the original
copy outside of the chroot, you have to be sure updates get reflected
inside the chroot.

NAMED_CONF_INCLUDE_FILES mentioned in the OP seems to be a SuSE-ism
and I didn't dig into whatever bearing it might have for maintenance
of the chroot.
-- 
tale

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

Thread

Re: /etc/bind.keys in a chrooted environment tale <d.lawrence@salesforce.com> - 2020-07-22 11:34 -0400

csiph-web