DNS

DNS 5 REFUSED vs 17 BADKEY

Both DNS 5 (REFUSED) and 17 (BADKEY) belong to the DNS Response Codes (RCODEs) category. 5 indicates that query refused. The name server refuses to perform the requested operation for policy reasons. Meanwhile, 17 means that key not recognized. The TSIG key name in the message is not configured on the server.

Beschreibung

Query refused. The name server refuses to perform the requested operation for policy reasons.

Wann Sie es sehen

The server rejected your query due to access control — for example, a recursive resolver that only serves its own network, or a zone transfer blocked by ACL.

Wie man es behebt

Check the server's allow-query, allow-recursion, or allow-transfer ACLs. If you are not authorized to use this resolver, switch to a public DNS service.

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 5: Query refused. The name server refuses to perform the requested operation for policy reasons.

2.

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

3.

You encounter 5 when the server rejected your query due to access control — for example, a recursive resolver that only serves its own network, or a zone transfer blocked by ACL.

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 5 (REFUSED): Check the server's allow-query, allow-recursion, or allow-transfer ACLs. If you are not authorized to use this resolver, switch to a public DNS service. 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