Guest

Preview Tool

Cisco Bug: CSCuo75748 - DHCP server fails to retry dynamic update for BADKEY error

Last Modified

Feb 26, 2015

Products (1)

  • Cisco Network Registrar

Known Affected Releases

8.2(0.1)

Description (partial)

Symptom:
DHCP Server will get BADKEY error when DNS Server is restarted after successful TKEY negotiation. 
The established keys are maintained in TKEY table which is non persistent. On BADKEY error, the failed dynamic update is not retried and new TKEY negotiation is done during the next dynamic update.

Conditions:
DNS Server is restarted after successful TKEY negotiation by the DHCP Server. Only the first dynamic update will fail due to BADKEY error.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.