Bind9 slave not updating Phone and sex chat lines

After we have installed BIND as a master DNS server (NS1) (as explained in my recent post), we can now try to set up a secondary DNS server (NS2) with BIND on Cent OS.NS2 acts as a backup if there are problems with NS1.

Result (if any): bind-dyndb-ldap plugin used to provision data from Identity Management DNS tree to the BIND Name Server updates DNS zone SOA serial number every time when the DNS zone or its record is modified, thus allowing Administrators to configure a slave DNS server for zones managed by Identity Management.

Once the zone transfer has been received and the zone has been updated, then this zone refresh is complete - named does not continue to try the other servers to see if one of them has a yet bigger SOA.

The frequency with which this type of refresh takes place is controlled by the settings in the zone's SOA record.

If a valid notify is received where the notify carries a serial number larger than the one in the SOA currently served by the slave then the slave zone will again schedule a zone refresh, following exactly the same process it would use if the zone refresh was initiated on timer - i.e.

it behaves exactly as if the zone refresh timer has expired.

Search for bind9 slave not updating:

bind9 slave not updating-82bind9 slave not updating-19bind9 slave not updating-20bind9 slave not updating-35

Please have the courtesy to check for responses and thank the people who helped you.

Leave a Reply

Your email address will not be published. Required fields are marked *

One thought on “bind9 slave not updating”