Opened 9 years ago

Closed 6 years ago

#966 closed enhancement (wontfix)

Notify should be configurable

Reported by: shane Owned by:
Priority: medium Milestone: Remaining BIND10 tickets
Component: xfrout Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

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.

Subtickets

Change History (3)

comment:1 Changed 9 years ago by shane

  • Milestone changed from New Tasks to Year 3 Task Backlog

comment:2 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:3 Changed 6 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check http://bundy-dns.de.

Closing ticket.

Note: See TracTickets for help on using tickets.