DNS 2 SERVFAIL vs 21 BADALG
Both DNS 2 (SERVFAIL) and 21 (BADALG) belong to the DNS Response Codes (RCODEs) category. 2 indicates that server failure. The name server encountered an internal error while processing the query. Meanwhile, 21 means that algorithm not supported. The cryptographic algorithm specified in the TKEY or SIG record is not supported by the server.
Descripción
Server failure. The name server encountered an internal error while processing the query.
Cuándo lo verás
The recursive resolver could not get an authoritative answer — commonly caused by DNSSEC validation failures, unreachable upstream nameservers, or misconfigured zones.
Cómo solucionarlo
Try a different resolver (e.g., 8.8.8.8 or 1.1.1.1) to isolate the issue. If you control the zone, check DNSSEC signatures, SOA serial consistency, and nameserver reachability.
Descripción
Algorithm not supported. The cryptographic algorithm specified in the TKEY or SIG record is not supported by the server.
Cuándo lo verás
Your TKEY negotiation or DNSSEC operation requested an algorithm (e.g., HMAC-SHA512) that the server has not been compiled with or configured to accept.
Cómo solucionarlo
Use a mutually supported algorithm. HMAC-SHA256 is widely supported for TSIG; for DNSSEC, check the server's supported algorithm list with its documentation.
Diferencias clave
DNS 2: Server failure. The name server encountered an internal error while processing the query.
DNS 21: Algorithm not supported. The cryptographic algorithm specified in the TKEY or SIG record is not supported by the server.
You encounter 2 when the recursive resolver could not get an authoritative answer — commonly caused by DNSSEC validation failures, unreachable upstream nameservers, or misconfigured zones.
You encounter 21 when your TKEY negotiation or DNSSEC operation requested an algorithm (e.g., HMAC-SHA512) that the server has not been compiled with or configured to accept.
Cuándo usar cada uno
For 2 (SERVFAIL): Try a different resolver (e.g., 8.8.8.8 or 1.1.1.1) to isolate the issue. If you control the zone, check DNSSEC signatures, SOA serial consistency, and nameserver reachability. For 21 (BADALG): Use a mutually supported algorithm. HMAC-SHA256 is widely supported for TSIG; for DNSSEC, check the server's supported algorithm list with its documentation.