DNS 10 NOTZONE vs 17 BADKEY
Both DNS 10 (NOTZONE) and 17 (BADKEY) belong to the DNS Response Codes (RCODEs) category. 10 indicates that name not contained in zone. A name used in the Prerequisite or Update section is not within the zone denoted by the Zone section. Meanwhile, 17 means that key not recognized. The TSIG key name in the message is not configured on the server.
Descrição
Name not contained in zone. A name used in the Prerequisite or Update section is not within the zone denoted by the Zone section.
Quando você o vê
Your dynamic update tried to modify a record that falls outside the zone specified in the update message (e.g., updating foo.example.org in the example.com zone).
Como corrigir
Ensure all names in the update are within the target zone. Check for typos in the zone name or the records being updated.
Descrição
Key not recognized. The TSIG key name in the message is not configured on the server.
Quando você o vê
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.
Como corrigir
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.
Diferenças principais
DNS 10: Name not contained in zone. A name used in the Prerequisite or Update section is not within the zone denoted by the Zone section.
DNS 17: Key not recognized. The TSIG key name in the message is not configured on the server.
You encounter 10 when your dynamic update tried to modify a record that falls outside the zone specified in the update message (e.g., updating foo.example.org in the example.com zone).
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.
Quando usar qual
For 10 (NOTZONE): Ensure all names in the update are within the target zone. Check for typos in the zone name or the records being updated. 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.