Hello,
I have the following problem with bind:
it is configured to run as bind:bind and after every reboot of the system
all files and directories under /etc/namedb become owned by root:wheel so
bind is unable is unable to update it's zone files after dhcpd leases IP to
any given client. How to
On Wed, Feb 20, 2008 at 10:09:53AM +0200, Deian Popov typed:
Hello,
I have the following problem with bind:
it is configured to run as bind:bind and after every reboot of the system
all files and directories under /etc/namedb become owned by root:wheel so
bind is unable is unable to
Ruben de Groot writes:
I have the following problem with bind:
it is configured to run as bind:bind and after every reboot of the system
all files and directories under /etc/namedb become owned by root:wheel so
bind is unable is unable to update it's zone files after dhcpd leases
Thank you both, you solved the problem!
On Wed, Feb 20, 2008 at 3:17 PM, Robert Huff [EMAIL PROTECTED] wrote:
Ruben de Groot writes:
I have the following problem with bind:
it is configured to run as bind:bind and after every reboot of the
system
all files and directories
Deian Popov wrote:
Hello,
I have the following problem with bind:
it is configured to run as bind:bind and after every reboot of the system
all files and directories under /etc/namedb become owned by root:wheel so
bind is unable is unable to update it's zone files after dhcpd leases IP to
any
Hi there,
On 20/02/2008, Jordan Gordeev [EMAIL PROTECTED] wrote:
[...]
See /etc/rc.d/named and /etc/mtree/BIND.chroot.dist.
And please, next time don't be so quick on mailing [EMAIL PROTECTED]
IMO questions is exactly dedicated for this purpose. Of course the OP
could've solved the problem on
