Red Hat Bugzilla – Bug 9180
Named secondary transfer fails.
Last modified: 2008-05-01 11:37:54 EDT
User named (101.102) does not have permission to create entries in
/var/named/sec so the transfer from the master server fails.
Neither bind nor caching-nameserver create a /var/named/sec directory.
It was probably created by a user before you updated to b1?
Moved this bug to "All" architectures.
Linuxconf uses the /var/named/sec directory to store secondaries. I suppose
Linuxconf creates the directory, here are the permissions:
root@bilbo sec]# pwd
[root@bilbo sec]# ls -la
drwxr-xr-x 2 root root 4096 Feb 11 12:27 ./
drwxr-xr-x 3 root root 4096 Feb 11 12:27 ../
Here is the error from /var/log/messages:
Feb 11 12:28:41 bilbo named: Forwarding source address is [0.0.0.0].1039
Feb 11 12:28:41 bilbo named: named startup succeeded
Feb 11 12:28:41 bilbo named: group = 234
Feb 11 12:28:41 bilbo named: user = named
Feb 11 12:28:41 bilbo named: Ready to answer queries.
Feb 11 12:28:41 bilbo named-xfer: can't make tmpfile
(sec/test.redhat.com.Xvai9i): Permission denied
I suppose since named runs as user named, it doesn't have permission. It looks
like named ran as root in 6.1... Should we move this bug to Linuxconf?
So it's a linuxconf bug... Reassigning.
Closing because we don't ship linuxconf anymore
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.