In CentOS 6.x and earlier, installing bind-chroot would automatically start named in the chrooted environment when starting named normally, for example with "service named start".<br />
<br />
In CentOS 7, if you "systemctl start named.service" with bind-chroot installed, it will NOT start named-chroot.service, it will instead start named.service which runs named outside of the chrooted environment.<br />
<br />
To get named to start in the chrooted environment, you must make sure named.service is stopped, then start named-chroot.service explicitly with "systemctl start named-chroot.service".<br />
<br />
This is likely to confuse administrators who are used to the old behavior. If bind-chroot is installed, then "systemctl start named.service" should start named-chroot.service instead (possibly as a dependency?).<br />
<br />
At the very least, a startup warning should be issued with something like "bind-chroot is installed, but you started named.service rather than named-chroot.service. Did you mean to run 'systemctl start named-chroot'?", or something to that effect.
↧