Red Hat Bugzilla – Bug 129389
named cannot start - config files not in chroot
Last modified: 2007-11-30 17:10:47 EST
Description of problem:
By default named now starts inside a chroot (good thing), however its
config files are OUTSIDE of the chroot, so named cannot start.
A simple fix would be to make sure named.conf named.custom and
rndc.key are in /var/named/chroot/etc and have rpm put symlinks in /etc.
Version-Release number of selected component (if applicable):
This is now fixed in bind-chroot-9.2.4rc6-6 .
On install, bind-chroot will replace these files:
with links to corresponding files in /var/named;
On uninstall, they are replaced back.
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.