The *named-chroot* service now starts correctly
Due to a regression, the "-t /var/named/chroot" option was omitted in the `named-chroot.service` file. As a consequence, if the `/etc/named.conf` file was missing, the *named-chroot* service failed to start. Additionally, if different `named.conf` files existed in the `/etc/` and `/var/named/chroot/etc/` directories, the "named-checkconf" utility incorrectly checked the one in the changed-root directory when the service was started. With this update, the option in the service file has been added and the *named-chroot* service now works correctly.