FS#31837 - [bind] wrong permissions on /var/named

Attached to Project: Arch Linux
Opened by Eric Griffith (EGriffith92) - Monday, 08 October 2012, 04:31 GMT
Last edited by Gaetan Bisson (vesath) - Friday, 12 October 2012, 01:32 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Gaetan Bisson (vesath)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Just installed bind last night (10/8/12, version 9.9.9.P3-1 as reported by pacman -Qs) to use as a dns-caching server. Started the daemon via systemd, ran status on the daemon just to make sure everything was fine. And it reported that wroking directory was not writable. As it turns out "Working directory" is /var/named. ls -l on /var, the directory named is owned by root, group is named. Group can read the directory but not write. simple "sudo chmod g+w named" fixed that issue but it shouldn't happen to begin with. When the package is installed it should make sure that /var/named is either owned by named:named or ensure that group has write permissions, not just read.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Friday, 12 October 2012, 01:32 GMT
Reason for closing:  Not a bug
Comment by Gaetan Bisson (vesath) - Monday, 08 October 2012, 05:43 GMT
It is good practice not to give named write access to /var/named unless specifically required. The default configuration works fine as it is and if you modify it in a way that relies on /var/named being writeable, you are expected to chmod it yourself.

As an aside, unless you need BIND's complex DNS features (which you do not for a simple caching server), I strongly suggest you use lightweight alternatives with better security records. These includes unbound (a real resolving server, which you can use as caching server out of the box) and dnsmasq (a non-resolving, caching server with other capabilities such as DHCP server).

Loading...