Xfrout notify question

[JINMEI Tatuya / 神明達哉]

At Wed, 23 May 2012 20:28:12 +0000,
"Spain, Dr. Jeffry A." <spainj at countryday.net> wrote:

> Thus I suggest the following. Keep the current behavior as a default if you wish, but add configuration commands to turn that behavior off and set up explicitly defined notification. For example
> > config set Xfrout notify <yes (default)|no|explicit>
> where "yes" means use the default behavior described above and also notify servers specified in an explicit notification list , "no" means don't send any notify messages, and "explicit" means notify only servers specified in an explicit notification list.
> 
> The notify-explicit configuration object would contain a list of explicit notification targets and associated TSIG key names:
> > config set Xfrout notify-explicit [{"target": "<IPv4/IPv6 address>", "key": "<key name>"},...]
> 
> Thanks for considering the addition of these features. They would certainly make my current setup work respond more efficiently to zone changes. Jeff.

BIND 9 has an option called 'also-notify', which I understand is what
you're basically suggesting (module how exactly it's enabled, etc).  I
believe we'll need to support it at some point anyway.  And I think
it's not that difficult to add to the current framework.  The question
is when we do this - we'll substantially revisit zone/data source
management as well as the relationship between xfrin/xfrout/zonemgr,
so if we do it right now, it's quite likely to reimplement (or at
least heavily modify) it in the new architecture.  So we may want to
hold off for a while.

With my understanding that manually invoked notify is working as a
workaround for you, "also-notify" can wait, e.g., for several months.
Am I understanding it correctly?

In any case, I'll open a ticket for this feature.

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.