Skip Menu |
Report information
The Basics
Id: 44753
Status: resolved
Priority: 50/50
Queue: dhcp-public

Bug Information
Version Fixed: 4.4.0
Version Found: (no value)
Versions Affected: (no value)
Versions Planned: 4.4.0
Priority: P1 High
Severity: (no value)
CVSS Score: (no value)
CVE ID: (no value)
Component: (no value)
Area: feature

Dates
Created:Fri, 24 Feb 2017 05:21:45 -0500
Updated:Wed, 13 Dec 2017 11:28:16 -0500
Closed:Wed, 13 Dec 2017 11:28:15 -0500



This bug tracker is no longer active.

Please go to our Gitlab to submit issues (both feature requests and bug reports) for active projects maintained by Internet Systems Consortium (ISC).

Due to security and confidentiality requirements, full access is limited to the primary maintainers.

Subject: Add "DDNS check-only" option for handling the TXT or DHCID guard RRs
This is associated with ticket #42620: Add "DDNS solo" option for operation of v4/v6 with prerequisites that ignore the other v6/v4 RRs and it introduces another perspective/use case from a production environment. Quoting the actual request: "This week we received a request from a customer to implement what they called a 'check only' method. They are only concerned with dynamic records overriding static records (which must be prevented) and they don't care if dynamic records get 'hijacked'. They suggested that the TXT record value should not be checked in this method, but only if it exists or not. If it exists, then it is a dynamic record and it can be overwritten. If it does not exist, then this record is static and can't be updated. Their use case is for users that roam between shared docking stations."