Updating the transfer rule
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.
This statement saves bandwidth at the expense of increased CPU and memory consumption.
Sets a maximum size in bytes (may take the case insensitive k or m shortforms) for each journal file.
// 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.
This statement may be used in a zone, view or global options clause.
This statement may be used in zone, view or an options clause.If a global notify statement is 'no' this statement may be used to override it for a specific zone and, conversely, if the global options contain a also-notify list, setting notify 'no' in the zone will override the global option.This statement may be used in normal zone, view or a global options clause.allow-notify applies to slave zones only and defines a match list, for example, IP address(es) that are allowed to NOTIFY this server and implicitly update the zone in addition to those hosts defined in the masters option for the zone.The default behaviour is to allow zone updates only from the masters IP(s).
This statement is mutually exclusive with update-policy and applies to master zones only.