Red Hat Bugzilla – Bug 156797
/etc/init.d/named does not check booleans.local
Last modified: 2007-11-30 17:11:05 EST
Description of problem:
OK, stuff was added to selinux and bind to support permitting dynamic dns
updating from dhcpd and this worked at one time. Unfortunately for bind,
selinux (and system-config-securitylevel) changed how locally modified
"variables" were set. Whereas /etc/selinux/targeted/booleans was modified
previously, now /etc/selinux/targeted/booleans is not chenged and local changes
are put in /etc/selinux/targeted/booleans.local.
Unfortunately, bind was not updated for this change. /etc/init.d/named needs to
be changed to check for BOTH /etc/selinux/targeted/booleans and
/etc/selinux/targeted/boolenas.local for the value of named_write_master_zones.
Version-Release number of selected component (if applicable):
FC4T2 updated to development as of 3 May 2005
NOTE: If named_write_master_zones is specified in
/etc/selinux/targeted/booleans.local, then this value (0 or 1) dominates and
anything in /etc/selinux/targeted/booleans is ignored. If not specified in
/etc/selinux/targeted/booleans.local, then the value in
/etc/selinux/targeted/booleans will rule.
NOTE: "targeted" and "strict" should work the same but I doubt that strict is as
OK, I'll make the next version of the named initscript check
This is now fixed with bind-9.3.1-4 in rawhide-2005-05-18 / FC4
Closing bugs in MODIFIED state from prior Fedora releases. If this bug persists
in a current Fedora release (such as Fedora Core 5 or later), please reopen and
set the version appropriately.