On Mon, December 3, 2007 23:44, Philip M. Gollucci wrote:
> Philip M. Gollucci wrote:
>> Gelsema, P (Patrick) - FreeBSD wrote:
>>> Ok.. In the /var directory there is no dump directory. So solving this
>>> I
>>> should do the following:
>>>
>>> hulk# mkdir /var/dump
>>> hulk# chown bind:bind /var/d
Philip M. Gollucci wrote:
> Gelsema, P (Patrick) - FreeBSD wrote:
>> Ok.. In the /var directory there is no dump directory. So solving this I
>> should do the following:
>>
>> hulk# mkdir /var/dump
>> hulk# chown bind:bind /var/dump
Well, if its relative to the chroot, its
/var/named/var/dump
--
Gelsema, P (Patrick) - FreeBSD wrote:
> Ok.. In the /var directory there is no dump directory. So solving this I
> should do the following:
>
> hulk# mkdir /var/dump
> hulk# chown bind:bind /var/dump
>
> Is that correct?
I believe so.
>
> Whilst I am on the BIND topic, does BIND automatically r
On Mon, December 3, 2007 23:29, Philip M. Gollucci wrote:
>> When I change the ownership, problem goes away.
>> How can I get the problem away without changing the ownership?
> in the options {} section
> what do you have for:
>
> options {
> // Relative to the chroot directory
> // n
> When I change the ownership, problem goes away.
> How can I get the problem away without changing the ownership?
in the options {} section
what do you have for:
options {
// Relative to the chroot directory
// named_chrootdir="/var/named"
directory "/etc/namedb";
On Mon, December 3, 2007 23:03, Philip M. Gollucci wrote:
> Gelsema, P (Patrick) - FreeBSD wrote:
>> In /etc/rc.conf I got the following.
>> hulk# cat /etc/rc.conf | grep named
>> named_enable="YES"
>> named_uid="bind"
>> named_chrootdir="/var/named"
> grep named /etc/defaults/rc.conf
> # named. I
Gelsema, P (Patrick) - FreeBSD wrote:
> In /etc/rc.conf I got the following.
> hulk# cat /etc/rc.conf | grep named
> named_enable="YES"
> named_uid="bind"
> named_chrootdir="/var/named"
grep named /etc/defaults/rc.conf
# named. It may be possible to run named in a sandbox, man security for
named_e
