Opened 3 years ago

Last modified 3 years ago

#4519 new enhancement

Add support for using DUIDs from v4/client-ids for use in DDNS updates RFC 4703 sec 5.2

Reported by: tmark Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: ddns Version: git
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DHCP Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


Per RFC 4703, Sec 5.2, If v4 and v6 clients cn use the same FQDN if the v4 clients embed the same value for DUID in the client_id (per RFC 4361).

The NameChangeRequest? generator function for v4 leases:

void queueNCR(const dhcp_ddns::NameChangeType& chg_type, const Lease4Ptr& lease);

needs to be able to extract the DUID from the client_id. This should be controllable via a parameter to the function ane we'll need a D2 client-side configuration knob for this.

The DNS updates that D2 constructs already limit themselves to either A or AAAA records based on protocol indicated in the NCR.

In order to support this behavior, the function for generating NameChangeRequests? for v4 leases needs to be modified


Change History (2)

comment:1 Changed 3 years ago by tmark

This ticket stems from issues Infoblox raised with ISC_DHCP:

Where they are looking for ways to support clients which do NOT conform with RFC 4361 above.
There is an associated bug ticket:

comment:2 Changed 3 years ago by hschempf

  • Milestone changed from Kea-proposed to Outstanding Tasks

per team meeting june 16, move to outstanding

Note: See TracTickets for help on using tickets.