BIND 10 #3362: d2::NameRemoveTransaction should check for NXRRSET not NXDOMAIN
BIND 10 Development
do-not-reply at isc.org
Fri Mar 7 18:31:11 UTC 2014
#3362: d2::NameRemoveTransaction should check for NXRRSET not NXDOMAIN
-------------------------------------+-------------------------------------
Reporter: tmark | Owner:
Type: defect | UnAssigned
Priority: high | Status:
Component: dhcp-ddns | reviewing
Keywords: | Milestone: DHCP-
Sensitive: 0 | Kea0.9
Sub-Project: DHCP | Resolution:
Estimated Difficulty: 4 | CVSS Scoring:
Total Hours: 0 | Defect Severity: N/A
| Feature Depending on Ticket:
| Add Hours to Ticket: 2
| Internal?: 0
-------------------------------------+-------------------------------------
Changes (by tmark):
* hours: 0 => 2
* owner: => UnAssigned
* status: new => reviewing
Comment:
This change was straight forward. The !NameRemoveTransaction code was
already
structured to treat RCODEs indicating the DNS data to be removed doesn't
exist
as success. It was merely checking for the wrong return value. The
change
simply replaces checks for NXDOMAIN with checks for NXRRSET in the
appropriate
places and tests.
This has been tested successfully against a BIND9 server.
{{{
7xx. [bug] tmark
b10-dhcp-ddns now treats a DNS server response code of NXRRSET as a
successful outcome when processing a request to remove DNS data. This
corrects a defect in which the server would incorrectly fail a request
to remove DNS data when the DNS server's response was NXRRSET.
(Trac #3362, git TBD)
}}}
--
Ticket URL: <https://bind10.isc.org/ticket/3362#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list