NOTIFY patch for 1.1.0
Status: Beta
Brought to you by:
bboy
Menu
▾
▴
#15 NOTIFY patch for 1.1.0
This patch add code that will handle notification of slaves when a dynamic update is applied.
The code is a MEGA patch please think carefully before installing it.
It requires a schema update in the SOA table to operate. There needs to be an also_notify column added which contains additional slaves (ALA Bind 9)
The config file get 3 extras entries.
notify-enabled a boolean which if not set on means the code does not happen
The schema addition is unnecessary if this is turned off.
notify-source The IP address of the interface to notify from - do no set unless absolutely necessary
notify-source6 The IPv6 address of the interface to notify from - ditto
The schema entry is for a char(255) column in the soa table. I have placed it at the end of the standard columns in my implementation but as the code retrieves it separately it can go anywhere suitable.
The patch affects a large proportion of the main code for the daemon as is introduces additional task scheduling code - a NOTIFY is a backwards query and needs to operate differently. The code has been written to allow slaves to time out, to allow for update storms to suppress (and notice) multiple updates and to keep the load on the server from zone transfers "sensible".
I will be adding a feature to allow the server to issue an update on all zones for which it is a master on start up and hopefully will be extending things to have IXFR capability available.
Currently this patch assembles its own records locally. I am considering enhancing it to use the task code and making that more general. To follow if I remember.
patch to add NOTIFY facility to1.1.0