It looks like BIND9, as delivered in the base, has problems when zones are using dynamic DNS updates. This is because it runs as user "bind", but that user doesn't have write access to /var/named/etc/namedb/master - the script /etc/rc.d/named uses mtree to set that directory as follows: drwxr-xr-x 2 root wheel 512 Nov 2 22:40 master So, if I try to do a DNS-update (in this case using "nsupdate"-command") I get the following error in /var/log/all.log: Nov 2 22:40:31 vimes named[98525]: client 213.187.177.2#54260: updating zone 'aminor.no/IN': adding an RR at 'jolie.aminor.no' A Nov 2 22:40:31 vimes named[98525]: journal file master/aminor.no.zone.jnl does not exist, creating it Nov 2 22:40:31 vimes named[98525]: master/aminor.no.zone.jnl: create: permission denied Nov 2 22:40:31 vimes kernel: Nov 2 22:40:31 vimes named[98525]: master/aminor.no.zone.jnl: create: permission denied Nov 2 22:40:31 vimes named[98525]: client 213.187.177.2#54260: updating zone 'aminor.no/IN': error: journal open failed: unexpected error If on the other hand I start BIND9 as usual and then change the owner of the "master"-directory so it's owned by user "bind", the nsupdate works as expected. It's not meant to be like this, is it? -- Regards / Hilsen Eivind Olsen <eivind_at_aminor.no>Received on Tue Nov 02 2004 - 20:56:33 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:20 UTC