DNS

DNS 1 FORMERR vs 17 BADKEY

Both DNS 1 (FORMERR) and 17 (BADKEY) belong to the DNS Response Codes (RCODEs) category. 1 indicates that format error. The name server was unable to interpret the query due to a malformed DNS message. Meanwhile, 17 means that key not recognized. The TSIG key name in the message is not configured on the server.

Beschreibung

Format error. The name server was unable to interpret the query due to a malformed DNS message.

Wann Sie es sehen

Your DNS client or library sent a query the server could not parse, often caused by a buggy resolver, corrupted packet, or unsupported EDNS options.

Wie man es behebt

Check your DNS client or library version for known bugs. Capture the raw query with dig or Wireshark and verify it conforms to the DNS wire format.

Beschreibung

Key not recognized. The TSIG key name in the message is not configured on the server.

Wann Sie es sehen

Your TSIG-signed query or update references a key name that the server does not have in its keyring, so it cannot verify the signature.

Wie man es behebt

Ensure the TSIG key name matches exactly (case-sensitive) on both client and server. Add the missing key to the server's configuration if it is a new key.

Wesentliche Unterschiede

1.

DNS 1: Format error. The name server was unable to interpret the query due to a malformed DNS message.

2.

DNS 17: Key not recognized. The TSIG key name in the message is not configured on the server.

3.

You encounter 1 when your DNS client or library sent a query the server could not parse, often caused by a buggy resolver, corrupted packet, or unsupported EDNS options.

4.

You encounter 17 when your TSIG-signed query or update references a key name that the server does not have in its keyring, so it cannot verify the signature.

Wann welchen verwenden

For 1 (FORMERR): Check your DNS client or library version for known bugs. Capture the raw query with dig or Wireshark and verify it conforms to the DNS wire format. For 17 (BADKEY): Ensure the TSIG key name matches exactly (case-sensitive) on both client and server. Add the missing key to the server's configuration if it is a new key.

Mehr erfahren