Project

General

Profile

Bug #6622

DHCP Server: Dynamic DNS required fields are ambiguous

Added by Thomas Ward over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Very Low
Category:
DHCP Server
Target version:
Start date:
07/17/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

This is a screenshot of the current DHCP Server's advanced Dynamic DNS options, as of 2.3.1-p5:

For the Domain key secret, the pfSense system requires this to be a key made with the HMAC-MD5 algorithm.

Not knowing what algorithm is needed here, I was using HMAC-SHA512 for all my DNS keys. After three hours of poking, I realized it needs to be HMAC-MD5, and fixed that issue.

I would suggest putting in the description for "DNS Domain key secret" that this has to be an HMAC-MD5 key. Or, implement related feature request #6621 (https://redmine.pfsense.org/issues/6621).

Associated revisions

Revision 4d55ef96 (diff)
Added by Chris Buechler over 3 years ago

Clarify that HMAC-MD5 key is required. Ticket #6622

Revision cadcc898 (diff)
Added by Chris Buechler over 3 years ago

Clarify that HMAC-MD5 key is required. Ticket #6622

History

#1 Updated by Chris Buechler over 3 years ago

  • Category set to DHCP Server
  • Status changed from New to Resolved
  • Assignee set to Chris Buechler
  • Priority changed from Normal to Very Low
  • Target version set to 2.3.2
  • Affected Version set to All

Thanks, committed clarification to description.

Also available in: Atom PDF