Updating the transfer rule
While this statement would normally be used in a zone of type 'master' there is nothing to prevent its use in a 'slave' zone - in which case the NOTIFY would be triggered following a zone transfer to the slave. Defines an alternative local IP address to be used for inbound zone transfers by the server if that defined by transfer-source (transfer-source-v6) fails and use-alt-transfer-source is enabled.This address must appear in the remote end's allow-transfer statement for the zone being transferred.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.masters-list may be used to reference a list of servers (slaves) defined in a masters clause each of which will be sent a NOTIFY.The key-name field defines the key to be used to authenticate the NOTIFY when using TSIG and references the name of a key clause; a corresponding key clause with the same key-name must be present in the slave server(s) for the zone.
This statement may be used in zone, view or an options clause.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.The gp-num parameter changes the port number used for NOTIFY for all the listed servers (the default is port 53).
The p-num parameter changes the port number for the specific IP address only.
This statement may be used in a zone, view or global options clause.