20
BADNAME
Duplicate Key Name
Extended RCODE (EDNS0)RFC 2930
BADNAME (20) is returned during TKEY key establishment when the key name proposed by the client already exists on the server. TKEY key names must be unique per RFC 2930. This indicates a collision or reuse attempt for an existing TKEY name.
RCODE
20
Name
BADNAME
Standard
RFC 2930
Description
During TKEY negotiation, the client proposes a name for the new shared key. If a key with that name already exists in the server's key storage, the server returns BADNAME. This prevents duplicate key names which would create ambiguity in TSIG processing. The client should generate a unique name (typically including a timestamp or random component) for each new TKEY establishment. BADNAME is rare in practice.
Common Causes
- –TKEY name proposed by client already exists on server
- –Key name collision in TSIG/TKEY key store
- –Client reusing a TKEY name without deleting the previous key