Bind9 not updating zone speed dating derry northern ireland
The format of also-notify changed in BIND9.9 to that shown below. The also-notify statement is relevant only with master zones and defines one or more IP addresses, and optional port numbers, of servers that will be sent a NOTIFY when the master zone file is reloaded.
The receiving slave controls which port number and which addresses it will accept NOTIFY messages from using the allow-notify statement or the masters statement.
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-update defines an address_match_list of hosts that are allowed to submit dynamic updates for master zones, and thus this statement enables Dynamic DNS.
The default in BIND 9 is to disallow updates from all hosts, that is, DDNS is disabled by default.
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.
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.
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.
The allow-update in the first zone clause could have been omitted since it is the default behavior.