Previously named-chroot.service set-up chroot environment for the named before starting the daemon by mounting necessary files and directories to the /var/named/chroot path. However if the start-up of the daemon failed, the mounts were not unmounted, but stayed there. This way the chroot environment got messed up.
Note that also named-sdb-chroot.service used the same chroot path and suffered from the same imperfection.
named-chroot.service and named-sdb-chroot.service have been modified and the chroot set-up code has been separated into new systemd service:
- named-chroot-setup.service (for named)
- named-sdb-chroot-setup.service (for named-sdb)
As an addition named-sdb now uses its own chroot path '/var/named/chroot_sdb' and has been separated into its own subpackage 'bind-sdb-chroot' and is NOT a part of 'bind-chroot' package any more. Users that want to use named-sdb in the chroot have to install the 'bind-sdb-chroot' package.