BIND9 dump file

[Gerard Samuel]

Gerard Samuel wrote:

> Im getting a bunch of these in the logs ->
> Nov 10 10:30:48 gatekeeper named[312]: dumping master file: 
> master/tmp-SLtSQEmBBK: open: permission denied
>
> So I figured a filesystem permissions problem.  I chowned
> /var/named/etc/namedb/master to bind:wheel.
> But when the box gets rebooted, the directory goes back to root:wheel.
> Im currently using BIND9 only for the LAN (cacheing dns).
>
> Thanks for any info that you may provide...

Im confused.  I've read the named and rc.conf man pages, and didn't find out
why named is behaving as it is.
I've tried adding ->
named_chroot_autoupdate="NO"
to /etc/rc.conf, but its still generating those logs.

>
> /etc/rc.conf
> -- 
> named_enable="YES"
> named_chrootdir="/var/named"
>
> /var/named/etc/namedb/named.conf
> -- 
> options {
>        directory       "/etc/namedb";
>        pid-file        "/var/run/named/pid";
>        dump-file       "/var/dump/named_dump.db";
>        statistics-file "/var/stats/named.stats";
>        forward only;
>        forwarders {
>                w.x.y.z; a.b.c.d;
>        };
> };
>
> key DHCP_UPDATER {
>        algorithm HMAC-MD5.SIG-ALG.REG.INT;
>        secret my_key_here;
> };
>
> zone "." {
>        type hint;
>        file "named.root";
> };
>
> zone "0.0.127.IN-ADDR.ARPA" {
>        type master;
>        file "master/localhost.rev";
> };
>
> zone "trini0.org" {
>        type master;
>        file "master/trini0.org";
>        allow-update { key DHCP_UPDATER; };
> };
>
> zone "0.168.192.in-addr.arpa" {
>        type master;
>        file "master/trini0.org.rev";
>        allow-update { key DHCP_UPDATER; };
> };
>
> // RFC 3152
> zone 
> "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA" 
> {
>        type master;
>        file "master/localhost-v6.rev";
> };
>
> // RFC 1886 -- deprecated
> zone 
> "1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.INT" 
> {
>        type master;
>        file "master/localhost-v6.rev";
> };