This service will be undergoing maintenance at 20:00 UTC, 2017-04-03. It is expected to last about 30 minutes
Bug 455894 - Write problem to journalizing files after updating Bind
Write problem to journalizing files after updating Bind
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: bind (Show other bugs)
8
All Linux
low Severity medium
: ---
: ---
Assigned To: Adam Tkac
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-18 12:57 EDT by Gijs
Modified: 2013-04-30 19:40 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-19 07:58:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Gijs 2008-07-18 12:57:16 EDT
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 07:58:38 EDT
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)

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