Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I installed a test vmware network running a win2k8 R2 DC and 3 rhel5 nodes. the DC is working as the master DNS as well.
I configured one rhel5 to become the slave name server of the DC. When I start the named for the first time it create the slave zone file correctly in the zones dir but when i restart the named again (/etc/init.d/network restart) it gives "the working directory is not writable" message and any changes done in the master zone are not getting updated.
However after sometime I see another set of messages saying zone transfer is started and then it writes any updates in the master server to the slave zone file.
This is not a chroot setup and /var/named and all sub dirs are owned by named:named with 644. SELinux is in enforced mode and all messages (shown in sealert tool) are corrected.
I setup this using bind, bind-devel and caching only rpms in the rhel 5 dvd.
Any help on getting rid of this message and geetting the slave file to update immediately with bind restart is highly appreciated.