Updating bind dns records
This statement may be used in a zone, view or global options clause. IP address(es) that are allowed to transfer (copy) the zone information from the server (master or slave for the zone).
The default behaviour is to allow zone transfers to any host.
By default BIND9 will send NOTIFY messages to all the target names (right-hand names) that appear in NS RRs for the zone (this behaviour can be modified by the notify statement.
Note: The also-notify statement can appear in a zone file, in which case its scope is the single zone, or in an options clause, in which case its scope is all zones, or in a view clause, in which case it applies to all zones in the view.
This statement may be used in a zone, view or global options clause.
Defines how the server calculates incremental zone changes.
This statement may be used in zone, view or an options clause.// fragment // key clause is shown only for illustration and would // normally be included in the file key "update-key" ; .... zone "example.com" in; zone "example.org" in; In the zone, the reference to the key clause "update-key" implies that the application that performs the update, say nsupdate, is using TSIG and must also have the same shared secret with the same key-name.This statement may be used in a zone, view or an options clause.If set to yes when the server receives a new version of a slave file by a non-incremental zone transfer it will compare the new version to the previous one and calculate a set of differences.The differences are then logged in the zone's journal file (appended to zone file name) such that the changes can be transmitted to downstream slaves as an incremental zone transfer.