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
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/etc, you end up setting a
$BIND_CHROOT environment
Yes you can run without the chroot. Years ago it was considered best practice
to chroot and most power users would have said you were insane not to do so.
Now there are increasingly many who say it's not worth the effort (fairly easy
to get around in many cases) -- do a bit of google engineeri
-Original Message-
From: Harshith Mulky
To: "bind-users@lists.isc.org"
Subject: What is the use of having a chroot path during installation
of Bind
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 t
6 matches
Mail list logo
