Questions on bind-chroot

Lightner, Jeffrey JLightner at
Mon Jun 13 18:54:20 UTC 2016

Is this RHEL5?  RHEL6?  Something else?

On RHEL5 we had bind-chroot running and did all our edits directly in /var/named/chroot/etc for named.cocnf and /var/named/chroot/var/named for zone files.

In RHEL7 (which uses systemctl rather than service) they setup special mounting in the named-chroot systemd file so one has to be sure to restart that rather than just the named system file as the named by itself ignores your chroot setup.    In this RHEL7 setup you edit the named.conf in /etc itself (i.e. the non-chroot "real" path) and the "systemctl restart named-chroot" puts the mount of that file into /var/named/chroot/etc.

-----Original Message-----
From: bind-users-bounces at [mailto:bind-users-bounces at] On Behalf Of Tony Finch
Sent: Monday, June 13, 2016 11:04 AM
To: Harshith Mulky
Cc: bind-users at
Subject: Re: Questions on bind-chroot

Harshith Mulky <harshith.mulky at> wrote:

> Is it necessary for named.conf in the chroot path and /etc path to be 
> same

If they aren't the same, at some point in the future you or your colleagues are going to get very confused about which one is the right one.

> I have 2 different named.conf in both the paths and when I am running 
> the, service named restart, I see the named service starting from the 
> chroot path. Is that correct?

There isn't much standardization of BIND init scripts. Some of them try to keep in-chroot and out-of-chroot configuration in sync, some don't, maybe depending on how the script is configured. So I can't give you a direct answer; you should read your init script carefully.

f.anthony.n.finch  <dot at>  -  I xn--zr8h punycode Irish Sea: Cyclonic 3 or 4, increasing 5 at times. Smooth or slight, occasionally moderate in far south. Thundery showers, fog patches. Moderate or good, occasionally very poor.
Please visit to unsubscribe from this list

bind-users mailing list
bind-users at

More information about the bind-users mailing list