So? What is your question?
The working directory is not writable by default, indeed.
- Code: Select all
[root@xxxxxx ~]# ls -lhd /var/named/chroot/var/named
drwxr-x--- 4 root named 4.0K Jan 20 17:31 /var/named/chroot/var/named
These are the default settings named
comes with (at least, I know I haven't changed them). I also have BIND running on my home machine for almost a year now... and I never had any problems with such permission settings. Googleing for the error message from logs will lead you to a solution to get rid of it - the first link to be exact. However, I'm no BIND expert to tell you what the right permissions and file ownership would be for the folders and files coming with BIND. On the other hand, I can tell I only know of a few services requiring some permission changes in order to work properly ( assigning SUID to an executable), and BIND is not one of them, so I prefer to leave it as it is for now.