Date: Tue, 15 Dec 2009 05:14:39 +0000 (UTC) From: Doug Barton <dougb@FreeBSD.org> To: cvs-src-old@freebsd.org Subject: cvs commit: src/etc/mtree BIND.chroot.dist src/etc/namedb named.conf Message-ID: <200912150515.nBF5F4C7031723@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
dougb 2009-12-15 05:14:39 UTC
FreeBSD src repository
Modified files:
etc/mtree BIND.chroot.dist
etc/namedb named.conf
Log:
SVN rev 200563 on 2009-12-15 05:14:39Z by dougb
The named process needs to have a "working directory" that it can
write to. This is specified in "options { directory }" in named.conf.
So, create /etc/namedb/working with appropriate permissions, and
update the entry in named.conf to match.
In addition to specifying the working directory, file and path names
in named.conf can be specified relative to the directory listed.
However, since that directory is now different from /etc/namedb
(where the configuration, zone, rndc.*, and other files are located)
further update named.conf to specify all file names with fully
qualified paths. Also update the comment about file and path names
so users know this should be done for all file/path names in the file.
This change will eliminate the 'working directory is not writable'
messages at boot time without sacrificing security. It will also
allow for features in newer versions of BIND (9.7+) to work as
designed.
Revision Changes Path
1.7 +2 -0 src/etc/mtree/BIND.chroot.dist
1.30 +95 -95 src/etc/namedb/named.conf
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200912150515.nBF5F4C7031723>