Bug 455894

Summary:	Write problem to journalizing files after updating Bind
Product:	[Fedora] Fedora	Reporter:	Gijs <info>
Component:	bind	Assignee:	Adam Tkac <atkac>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	8	CC:	atkac, ovasik
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-07-19 11:58:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Gijs 2008-07-18 16:57:16 UTC

Description of problem:
The access rights and ownership of the zone/journalizing files are reset to
chmod 640 and the ownership to root:named after I update Bind. Because 'dynamic
updates' requires the named server to be able to write to the journalizing
files, these default access rights won't do.

Version-Release number of selected component (if applicable):
bind-9.5.0-28.P1.fc8
bind-9.5.0-27.rc1.fc8.i386

Steps to Reproduce:
1. yum update bind
  
Actual results:
The jnl files have ownership root:named, and chmods 640.

Expected results:
Either the jnl files have ownership named:named, or they have a chmod of 660.

Additional info:
I know the problem also occurred in former versions of Bind, but I'm not sure
which version exactly.

Comment 1 Gijs 2008-07-19 11:58:38 UTC

After consulting the FC list, "Christopher K. Johnson" mentioned that dynamic
zones should be placed inside the dynamic folder (/var/named/dynamic or
/var/named/chroot/var/named/dynamic)