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):
Steps to Reproduce:
1. ls -l /var/named/chroot/etc/
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
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
This was fixed in bind-9.2.4rc6-3 :
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.