First up is named/bind.
At first is wouldn’t start. I had numerous "permission denied" on the various config files. I changed ownership of /etc/named.conf and other config files and directories to group ownership ‘named’ and permissions g+rw (and +x for dirctiories). That got rid of the permission errors, but still I couldn’t start named. I got errors:
Jan 27 21:44:25 mail named[20626]: zone 'hprs.local.' allows unsigned updates from remote hosts, which is insecure
Jan 27 21:44:25 mail named[20626]: zone '0.168.192.in-addr.arpa' allows unsigned updates from remote hosts, which is insecure
Jan 27 21:44:25 mail named[20626]: the working directory is not writable
Jan 27 21:44:25 mail named[20626]: loading configuration: permission denied
Jan 27 21:44:25 mail named[20626]: exiting (due to fatal error)
In particular, the error "the working directory is not writable" was confusing. Which directory?
I think I found the answer here: https://github.com/sameersbn/docker-bind/issues/96. In summary, it says, "This happens because bind9 9.16.1 needs to write some files into the current directory as the bind user." Since I was running this manually from /etc, I tried changing to /tmp and running rc.bind from that, and that worked!
Question: in examining /etc/rc.d/rc.bind, I see no change of directory to something named can write to. named’s home directory is /var/named, but apparently rc.bind does not cause named to use that as a working directory.
I’m considering modifying rc.bind to cd /tmp, but this strikes me as a kludge. Surely Slackware users are able to run rc.bind and successfully launch named without doing that.
What’s the trick?