Ownership of /var/named Changes on Reboot.

Matthew Seaman m.seaman at infracaninophile.co.uk
Thu Jun 17 07:47:34 UTC 2010

Hash: SHA1

On 17/06/2010 04:21:34, Peter Boosten wrote:
> On 17-6-2010 4:58, Robert Huff wrote:
>> Martin McCormick writes:
>>>  	Is there a way to keep /var/named owned by bind across
>>>  reboots?
>> 	Yes.  I had this happen for a long time.
>> 	The bad news is it had been years since I fixed it, and I no
>> longer remember exactly what I did.  I will keep trying.
> Permissions are set using the mtree files:
> /etc/mtree/

Furthermore, the default setup *is* for named to run as an unprivileged
process.  The setup is very carefully designed so that named doesn't
have write permission on the directory where its configuration files are
stored, or on directories that contain static zone files, but it does
have write permission on directories it uses for zone files AXFR'd from
a master, or zone files maintained using dynamic DNS.

This used to generate a warning from bind about not having a writable
current working directory -- which was basically harmless and could be
ignored.  However recent changes mean bind needs a writable working
directory, so the latest layouts include /var/named/etc/namedb/working



- -- 
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
JID: matthew at infracaninophile.co.uk               Kent, CT11 9PW
Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/


More information about the freebsd-questions mailing list