Bind slave not updating

Specifically problems are encountered with updating slave zone database files, creating DDNS journal files and updating master zones from journals.It also manifests itself as named being unable to create custom log files.Once the primary master has processed the dynamic update and modified the zone, the slaves can get a new copy of it via zone transfers.Dynamic update permits more than the simple addition and deletion of records.So, to allow named to update slave or DDNS zone files, it is best to locate them in $ROOTDIR/var/named/slaves, with zone statements such as: zone "" IN ; zone "" IN ; To allow named to create its cache dump and statistics files, for example, you could use options statements such as: options ; 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.You can disable SELinux protection for named entirely by setting the 'named_disable_trans=1' SELinux tunable boolean parameter.

A dig on the primary (dig @ns1 domain.com) shows; ;; QUESTION SECTION: ; 86400 IN A 1.1.1.1 A dig on the 2ndary shows; ;; QUESTION SECTION: ; Nearly all ISPs assign addresses to dialup and cable modem customers using DHCP.To keep up, DNS needed to support the dynamic addition and deletion of records.While checking the file I see that the zone entry has not been updated at slave server.If I update it manually and reload named on slave then zone files (db files) are getting created without any issue and any modification at master server for the zone records are also getting updated.The SELinux policy particularly does NOT allow named to modify the $ROOTDIR/var/named directory, the default location for master zone database files.

837

Leave a Reply