Bug 596029 - Bind doesn't copy over named.conf to chroot; upgrading to F13 broke bind
Summary: Bind doesn't copy over named.conf to chroot; upgrading to F13 broke bind
Status: CLOSED DUPLICATE of bug 595025
Alias: None
Product: Fedora
Classification: Fedora
Component: bind
Version: 13
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Adam Tkac
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-26 07:18 UTC by D. Wagner
Modified: 2013-04-30 23:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-06-01 12:26:19 UTC
Type: ---

Attachments (Terms of Use)

Description D. Wagner 2010-05-26 07:18:35 UTC
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  ]
Starting named: 
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
  include "/etc/pki/dnssec-keys/dlv/dlv.isc.org.conf";
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):


Comment 1 D. Wagner 2010-05-26 08:09:28 UTC
"yum reinstall bind-chroot" does not fix this problem.  "yum reinstall bind" does not fix it, either.

Comment 2 Adam Tkac 2010-06-01 12:26:19 UTC
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 ***

Note You need to log in before you can comment on or make changes to this bug.