Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 85027 - chrooted named should be default, migration support missing
chrooted named should be default, migration support missing
Product: Red Hat Linux
Classification: Retired
Component: bind (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Walsh
Ben Levenson
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2003-02-24 18:16 EST by Heiner Westphal
Modified: 2007-04-18 12:51 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-08-01 16:05:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
shell script to migrate to chrooted named including syslog support (5.28 KB, text/plain)
2003-02-24 18:27 EST, Heiner Westphal
no flags Details

  None (edit)
Description Heiner Westphal 2003-02-24 18:16:04 EST
From Bugzilla Helper:

Description of problem:
The default configuration of bind should come with a chrooted named.
At least some support scripts should be provided, which make it easy
to migrate to a chrooted named.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Just start named or
2. try to setup a chrooted named which can be maintained with out of the box tools

Additional info:

Provide a chrooted named as standard setup (including tools support).
Use the attached script as a start for migrating a non chrooted
named to chroot:
Comment 1 Heiner Westphal 2003-02-24 18:27:06 EST
Created attachment 90333 [details]
shell script to migrate to chrooted named including syslog support

This was tested on Redhat 7.2 with bind 9.2.1-1.7x
and two times on redhat 8.0 with bind 9.2.1-9
always with ROOTDIR=/var/named and user=named.

The only official name server with this settings is
Comment 2 Heiner Westphal 2003-03-04 17:21:53 EST
The script depends on "strings" which belongs to binutils.
These are possibly not installed on a named only machine.

This is not really necessary.
Comment 3 Daniel Walsh 2003-03-26 15:38:31 EST
I have added a bind-chroot kit that when installed will cause bind to run in a
chroot environment.  It will be on Rawhide as soon as rawhide is available.
The source rpm is available on ftp://people.redhat.com/dwalsh.
This is experimental.  Your feedback is appreciated.


Note You need to log in before you can comment on or make changes to this bug.