Date: Wed, 20 Feb 2008 08:17:34 -0500 From: Robert Huff <roberthuff@rcn.com> To: Ruben de Groot <mail25@bzerk.org> Cc: Deian Popov <deianp@gmail.com>, freebsd-questions@freebsd.org Subject: Re: DNS /etc/namedb owner hell Message-ID: <18364.10350.642689.920407@jerusalem.litteratus.org> In-Reply-To: <20080220103358.GA14370@ei.bzerk.org> References: <bfc2b10c0802200009n710c70fbv18fe1f35378dfd33@mail.gmail.com> <20080220103358.GA14370@ei.bzerk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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 IP to > > any given client. How to fix either owner, or set somewhere that the owner > > of this folder, subfolder and files is my DNS server? > > Try setting named_chroot_autoupdate to NO in your rc.conf Does this still work if you don't run chrooted? To the OP: does this happen every reboot, or when you update the system? I used to have tha latter problem, and fixed it by adding NO_BIND_ETC= true # Do not install files to /etc/namedb to /etc/make.conf. Upsides: no permission mangling, and no automatic file update. Downside: no automatic file update, though you can deal with this using mergeaster. Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18364.10350.642689.920407>