Red Hat Bugzilla – Bug 1277820
bind doesn't start to due wrong systemd startup script
Last modified: 2015-11-08 01:50:38 EST
Description of problem:
The checking of the zone doesn't work correctly on startup
Version-Release number of selected component (if applicable):
Start bind ind chroot environment
Steps to Reproduce:
1. Create config in chroot environment with a zone file
Problem is missing chroot directory for zone file checking.
nano -w /usr/lib/systemd/system/named-chroot.service
#ExecStartPre=/bin/bash -c 'if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi'
ExecStartPre=/bin/bash -c 'if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf; else echo "Checking of zone files is disabled"; fi'
systemctl restart named-chroot
Please fix it urgently, it is a release showstopper
When using bind-chroot package, everything is prepared in a way so that you don't have to think about the chroot directory. This means that all zone files and configuration is bind-mounted automatically (by named-chroot-setup.service) into the chroot environment. This happens ONLY if the files and directories are NOT present inside the chroot environment before the bind-mount happens.
This means that you should keep the configuration in the standard places (/etc/named.conf, /var/named/*, etc.) and then just start the named-chroot.service.
If you copy the configuration into the chroot directory, then you'll have to modify the service files yourself. I'm not going to change the service files, since everything works when used in a way I described.
For more information, please refer to the "Running BIND in a chroot environment" section of https://docs.fedoraproject.org/en-US/Fedora/22/html/Networking_Guide/sec-bind-namedconf.html
OK, config was from a system before the automatismus was implemented and it had to be done manually. Worked well with FC22. Moved to standard bind config. Works well now. Thnx.
BTW: Doesn't it look like a bug then in FC22, because that changed from FC22 to FC23
ExecStartPre=/usr/sbin/named-checkconf -t /var/named/chroot -z /etc/named.conf
(In reply to Gerhard Wiesinger from comment #3)
> BTW: Doesn't it look like a bug then in FC22, because that changed from FC22
> to FC23
> ExecStartPre=/usr/sbin/named-checkconf -t /var/named/chroot -z
Good catch. Will fix it soon...
bind-9.10.3-2.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-aad2c8ec85
bind-9.10.3-2.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
$ su -c 'dnf --enablerepo=updates-testing update bind'
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-aad2c8ec85
bind-9.10.3-2.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.