Am 14.01.2016 um 22:37 schrieb John Miller:
On Thu, Jan 14, 2016 at 4:01 PM, Reindl Harald wrote:
normally anything is done with backends and scripts
Yep - via Puppet and scripting for us, mostly.
so after once configured it don't matter if things are bekow
/var/named/chroot/ or on a high
On Thu, Jan 14, 2016 at 4:01 PM, Reindl Harald wrote:
>
>
> Am 14.01.2016 um 21:48 schrieb John Miller:
>>
>> Thanks for the advice, Mike. We chrooted our install because it was
>> "best practice" security-wise, but from an administration standpoint,
>> it's been a bit of a headache: for example,
Am 14.01.2016 um 21:48 schrieb John Miller:
Thanks for the advice, Mike. We chrooted our install because it was
"best practice" security-wise, but from an administration standpoint,
it's been a bit of a headache: for example, you have to keep straight
what goes in /etc and /var/named/chroot/et
ommend it, but they do not explicitly
> discourage it.
> """
>
> From: on behalf of Harshith Mulky
>
> Date: Thursday, January 14, 2016 at 1:46 AM
> To: "bind-users@lists.isc.org"
> Subject: What is the use of having a chroot path during installati
14, 2016 at 1:46 AM
To: "bind-users@lists.isc.org<mailto:bind-users@lists.isc.org>"
mailto:bind-users@lists.isc.org>>
Subject: What is the use of having a chroot path during installation of Bind
Hello,
When installing bind, the following 2 are installed
bind-9.8.2-0.17.rc1.el6
Hello,
When installing bind, the following 2 are installed
bind-9.8.2-0.17.rc1.el6.x86_64
bind-chroot-9.8.2-0.17.rc1.el6.x86_64
What is the need of this bind-chroot?
I see all files in /var/named path are softlinks to /var/named/chroot/var/named
and
/etc/named.conf is softlink to /var/
6 matches
Mail list logo
