By default, named is not allowed by the SELinux policy to write, create or delete any files EXCEPT in these directories: where $ROOTDIR may be set in /etc/sysconfig/named if bind-chroot is installed.
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.So, to allow named to update slave or DDNS zone files, it is best to locate them in $ROOTDIR/var/named/slaves, with You can also tell SELinux to allow named to update any zone database files, by setting the SELinux tunable boolean parameter 'named_write_master_zones=1', using the system-config-securitylevel GUI, using the 'setsebool' command, or in /etc/selinux/targeted/booleans.So you could create a paper list and write the names and phone numbers on it. This works but gets to be a problem if the league expands and you get,for example, 10 teams.So an alternative is to create three lists one for team A , one for team B and one for team C.This tutorial is for beginners and you will learn: To Explain what zones and zone files and how they work are we are going to start with a simple analogy.
If you imagine that you (Bill) have organized a football league that has three teams.
This is a problem that has been reported when running BIND 9 on Red Hat Enterprise Linux or Fedora Core.
Specifically, problems are encountered with updating slave zone database files, creating DDNS journal files, and updating master zones from journals.
DNS is comprised logically of Domains but physically of zones.
A domain is a logical division of the DNS name space whereas a zone is physical, as the information is stored in a file called a zone file.
Is there a quick way to do this without iterating over each record with a delete action?