BIND 10 #966: Notify should be configurable
BIND 10 Development
do-not-reply at isc.org
Wed May 25 13:02:24 UTC 2011
#966: Notify should be configurable
-------------------------------------+-------------------------------------
Reporter: shane | Owner:
Type: enhancement | Status: new
Priority: major | Milestone: New
Component: xfrout | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
We should be able to configure notify behavior, both on a server and per-
zone level.
It should be possible to set explicit IP:port values, as well as something
like "figure out from NS RRSET" as a special target.
{{{
Xfrout/default_notify [ { "type":"FROM_NS_RRSET" } ]
Xfrout/zones[0]/notify [ { "type":"IP", "IP":"192.0.2.1", "port":5353 } ]
Xfrout/zones[1]/notify []
}}}
Here the default behavior would be to figure out who to notify from the NS
RRSET, while the first zone would have only an explicit notify, and the
second zone would not send any notifies at all.
--
Ticket URL: <http://bind10.isc.org/ticket/966>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list