Description of problem: in /var/named/chroot/etc/, named.conf and rndc.key are not pointing to /etc/named.conf and /etc/rndc.key Version-Release number of selected component (if applicable): 7.2-12 How reproducible: Ever Steps to Reproduce: 1. ls -l /var/named/chroot/etc/ Actual results: Blank files Expected results: Hard links to /etc/named.conf and /etc/rndc.key
I forgot to say that if the /etc/named.conf and /etc/rndc.key as well as the /var/named/ zone files aren't the same files on the chroot environment, named can't be stopped and restarted because rndc isn't working. It can't even re-read the config files, if you want it do so without stopping the service. Another solution can be to put those files in the chroot environment and then symlink those in /etc and /var/named, like this: /etc/rndc.key -> /var/named/chroot/etc/rndc.key /etc/named.conf -> /var/named/chroot/etc/named.conf etc. etc.
This was fixed in bind-9.2.4rc6-3 : the /var/named/chroot/etc/{named.conf,rndc.key} files were getting created as blank files; they are now always copied from /etc . Perhaps they should be hardlinks; but some people might want different configs for a chroot environment than for the non-chroot environment.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2004-568.html