Re: [CentOS] Bind data directory borked on update from 5.3 to 5.4

Kai Schaetzl wrote:

Brian Mathis wrote on Thu, 21 Jan 2010 09:38:12 -0500:

...

I don't think you'd want a compromised named to be able to make changes to your authoritative DNS records, which is what could happen if you have permissions set that way.

But why does named then report it right after the update?

Jan 21 12:46:40 chacha named[16607]: the working directory is not writable

I experienced same message when upgrading bind on freebsd recently. After googling, I settled down, seems that its exactly as it must be. Only that message shold be more precise and add at the end something like "... good!".