Red Hat Bugzilla – Bug 184065
Slave files placed in wrong directory - permission prevents zone transfer
Last modified: 2008-04-29 07:34:01 EDT
Description of problem:
1. By default, slave zone files are placed in /var/named (or
/var/named/cache/var/named if bind-chroot is installed)
2. /var/named is owned by root:named with permission 0750 so the zone transfer
fails because the slave zone file cannot be opened
3. According to bug 184035, slave zones should be placed in /var/named/slave,
which is owned by named:named
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a slave zone for a valid master.
2. Save the configuration.
- Zone does not transfer
- Error messages indicating that the slave zone file can't be opened (created)
are found in /var/log/messages
- The zone should transfer
prepend 'slave/' to the name of slave zone files
Yes, you're right - s-c-b should prompt users to prepend 'slaves/' to the location
of slave or DDNS updateable zone files - the next version (s-c-b-4.0.0-40) will
do this - thanks.
This bug is now fixed with system-config-bind-4.0.0-40_FC5, available from:
When you add a slave zone, the default zone file is now prefixed with slaves/,
and you will be warned if you create a slave zone file not in slaves/ .
When you make a zone dynamically updateable by adding an 'allow-update' clause,
the GUI will prompt to be allowed to move the zone file to slaves/ .
From User-Agent: XML-RPC
system-config-bind-4.0.0-40_FC4 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
Can anybody reproduce this bug in Fedora 8?
This seems fixed in current version. Closing the bug.