[Bug 922608] New: Setting up named-chroot using setup-named-chroot not documented

[bugzilla at redhat.com]

Product: Fedora Documentation
https://bugzilla.redhat.com/show_bug.cgi?id=922608

            Bug ID: 922608
           Summary: Setting up named-chroot using setup-named-chroot not
                    documented
           Product: Fedora Documentation
           Version: devel
         Component: deployment-guide
          Severity: high
          Priority: unspecified
          Assignee: jhradile at redhat.com
          Reporter: harker-redhat at harker.com
        QA Contact: docs-qa at lists.fedoraproject.org
                CC: dhensley at redhat.com, oglesbyzm at gmail.com

Description of problem:
In FC18 completely changed you configure the named-chroot package.

In RHEL when you install the named-chroot package, the /var/named/chroot
environment gets setup automatically.

In FC18 installing named-chroot package does not set up the /var/named/chroot
environment.

In FC18 you need to initialize the /var/named/chroot environment by running:
    /usr/libexec/setup-named-chroot.sh /var/named/chroot on 

I suspect this change was made with the transition to systemd.


Version-Release number of selected component (if applicable):
bind-chroot.x86_64                  32:9.9.2-8.P1.fc18

How reproducible:
www.google.com/search?q=setup-named-chroot&as_sitesearch=fedoraproject.org

Steps to Reproduce:
Search:
www.google.com/search?q=setup-named-chroot&as_sitesearch=fedoraproject.org

Actual results:
No results

Expected results:
Some documentation

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

# 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

# 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

-- 
You are receiving this mail because:
You are the QA Contact for the bug.