BIND 10 #3341: D2 should NOP updates in a given direction if no servers are defined for that direction
BIND 10 Development
do-not-reply at isc.org
Mon Feb 17 16:00:27 UTC 2014
#3341: D2 should NOP updates in a given direction if no servers are defined for
that direction
-------------------------------------+-------------------------------------
Reporter: tmark | Owner:
Type: defect | UnAssigned
Priority: medium | Status:
Component: dhcp-ddns | reviewing
Keywords: | Milestone: DHCP-
Sensitive: 0 | Kea0.9-alpha
Sub-Project: DHCP | Resolution:
Estimated Difficulty: 16 | CVSS Scoring:
Total Hours: 6 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 6
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by tmark):
* hours: => 6
* owner: tmark => UnAssigned
* status: assigned => reviewing
* totalhours: 0 => 6
Comment:
This is a straight forward change that allows D2 to be configured to
disable updates in one
a direction while allowing updates in the other direction to proceed.
Added methods to D2CfgMgr to return whether or not forward or reverse
updates are enabled.
Altered D2UpdateMgr::makeTransaction to utilize these new methods.
Added additional logs and unit tests.
ChangeLog suggested:
{{{
7xx. [func] tmark
b10-dhcp-ddns may now be configured to disable DNS updates in
in a given direction by simply not defining any domains for that
direction in its configuration. This allows it be configured to
support either forward DNS or reverse DNS only. Prior to this if
a request was received that could not be matched to servers in a
given direction it was failed immediately.
(Trac #3341, git TBD)
}}}
--
Ticket URL: <https://bind10.isc.org/ticket/3341#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list