Bug 922608

[bind] retire initscript in favour of systemd unit files (#719419)
http://lists.fedoraproject.org/pipermail/scm-commits/2012-January/728117.html

Using links to Fedora 17 Sysadmin Guide for discussion purposes as Fedora 18 Sysadmin Guide is not live.

I found the following reference to bind-chroot and /var/named/chroot:
docs.fedoraproject.org/en-US/Fedora/17/html/System_Administrators_Guide/index.html


and /var/named/chroot is also mentioned here:
http://docs.fedoraproject.org/en-US/Fedora/17/html/System_Administrators_Guide/ch-The_sysconfig_Directory.html#s2-sysconfig-named

I will write this up for comment and feedback.

The section in sysconfig-named just defines what can go into the /etc/sysconfig/named file.

It then points to section 12.2 of the sys admin guide which has nothing on setting up or using a chroot environment.  The setup procedure has changed with the advent of systemd

Created attachment 754538 [details]
1st draft for discussion

(In reply to Robert Harker from comment #0)
> Additional info:
> Here are a set of steps I wrote about setting named-chroot in FC18:
> 
> # Steps to set up a named in a chroot environment in FC18
> 
> # Install the packages
> yum install bind bind-chroot

"yum install bind-chroot" is enough. bind-chroot Requires bind package,
so yum will cover this for you.

> # Enable chroot environment
> # Note: This is a significant change (in FC18)/(relating to systemd)
> /usr/libexec/setup-named-chroot.sh /var/named/chroot on 
> 
> # Check chroot environment
> ls -l /var/named/chroot/etc /var/named/chroot/var/named
> 
> # Optional:
> # You may also want to hard link named.conf and rndc.key from
> /var/named/chroot/etc to /etc.
> # Check with
> ls -li /etc/named.conf /var/named/chroot/etc/named.conf
> ls -li /etc/rndc.key /var/named/chroot/etc/rndc.key
> # Create hard links with (ln with no -s)
> ln /var/named/chroot/etc/named.conf /etc/named.conf
> ln /var/named/chroot/etc/rndc.key /etc/rndc.key

You don't have to do this at all! named-chroot.service will do everything
for you! To all you have to do is just run "systemctl start named-chroot"

> # Enable the named-chroot service
> # Note: If you are running named-chroot.service you do not run named.service
> # Note: This is a significant change (in FC18)/(relating to systemd)
> systemctl enable named-chroot.service
> systemctl start named-chroot.service
> # Check with
> systemctl status named-chroot.service
> 
> # For ease in named administration add yourself to group named
> useradd ???
> 
> Note: FC18 still uses the rndc command to manage named.  Systemd only
> start/stops the named daemon

systemd can also make BIND to reload it's configuration using rndc for you.
All you have to do is type "systemctl reload named-chroot"

Created attachment 755032 [details]
2nd draft after feedback.

Thank you for the feedback, improvements have been made.

(In reply to Stephen Wadeley from comment #6)
> Created attachment 755032 [details]
> 2nd draft after feedback.
> 
> Thank you for the feedback, improvements have been made.

Looks good. Simple as it gets... :)

commit bb9374c86e4685aed477a7cc893263301717ab5e
Author: Stephen Wadeley <swadeley>
Date:   Mon Jun 17 23:58:13 2013 +0200

    [Bug 922608] Setting up named-chroot using setup-named-chroot

A very straightforward and thorough coverage; QA PASS!