Red Hat Bugzilla – Bug 596029
Bind doesn't copy over named.conf to chroot; upgrading to F13 broke bind
Last modified: 2013-04-30 19:46:27 EDT
Description of problem:
I upgraded from F12 to F13 today, and afterwards, bind stopped working. I use a chrooted version of bind. My best guess at the cause of the problem is that the update to bind updated /etc/named.conf, but these updates were not copied over to /var/named/chroot/etc/named.conf.
Now I cannot start named; I get the following error:
# service named restart
Stopping named: [ OK ]
Error in named configuration:
/etc/named.conf:77: open: /etc/pki/dnssec-keys/dlv/dlv.isc.org.conf: file not found
There is no line 77 in /etc/named.conf; on the other hand, line 77 of /var/named/chroot/etc/named.conf is
and there is no such file on my filesystem. /etc/named.conf does not contain that problematic include line. I cannot run system-config-bind; it errors out with a similar error message.
Should there be some script that copies the latest version of all of the relevant files into the chroot environment (/var/named/chroot)?
Other information: As part of the upgrade, I did have to move /etc/named.conf.rpmnew to /etc/named.conf.
Version-Release number of selected component (if applicable):
"yum reinstall bind-chroot" does not fix this problem. "yum reinstall bind" does not fix it, either.
This is same issue as bug #595025. Can you reply to https://bugzilla.redhat.com/show_bug.cgi?id=595025#c1, please? Thank you.
*** This bug has been marked as a duplicate of bug 595025 ***