Bind slave zone not updating
Actually this file is copied to NS2 so, if NS1 is dead or has a problem, NS2 has a backup configuration.
Thank you The worst that can happen as a result of using 777 permissions on a folder or even a file, is that if a malicious cracker or entity is able to upload a devious file or modify a current file to execute code, they will have complete control over your blog, including having your database information and password. The above information is largely against lots of security and maintainability principles. This legacy document is here only to insure incoming links continue to work. Once configured, it will create slave zones on other servers and configure them to automatically update when changes are made on your Virtualmin server.The SELinux policy particularly does NOT allow named to modify the $ROOTDIR/var/named directory, the default location for master zone database files.
SELinux policy overrules file access permissions - so even if all the files under /var/named have ownership named:named and mode rw-rw-r--, named will still not be able to write or create files except in the directories above, with SELinux in Enforcing mode.
The SELinux named policy defines these SELinux contexts for named: named_zone_t : for zone database files - $ROOTDIR/var/named/*named_conf_t : for named configuration files - $ROOTDIR/etc/.*named_cache_t: for files modifiable by named - $ROOTDIR/var/ If you want to retain use of the SELinux policy for named, and put named files in different locations, you can do so by changing the context of the custom file locations .