DNS 11 DSOTYPENI vs 22 BADTRUNC
Both DNS 11 (DSOTYPENI) and 22 (BADTRUNC) belong to the DNS Response Codes (RCODEs) category. 11 indicates that dSO-TYPE Not Implemented. The DNS Stateful Operations (DSO) type in the request is not supported by the server. Meanwhile, 22 means that bad truncation. The TSIG record was truncated in a way that makes it impossible to verify the message signature.
Описание
DSO-TYPE Not Implemented. The DNS Stateful Operations (DSO) type in the request is not supported by the server.
Когда вы это видите
Your client attempted a DSO operation (like a keepalive or push subscription) that the server does not recognize or has not implemented.
Как исправить
Verify that both client and server support the same DSO-TYPE. Upgrade the server software or fall back to traditional DNS queries.
Описание
Bad truncation. The TSIG record was truncated in a way that makes it impossible to verify the message signature.
Когда вы это видите
A large DNS response was truncated (TC bit set) but the TSIG MAC was computed over the full message, making the truncated version unverifiable.
Как исправить
Retry the query over TCP to avoid truncation. If using UDP, ensure your EDNS buffer size is large enough to receive the full signed response.
Ключевые различия
DNS 11: DSO-TYPE Not Implemented. The DNS Stateful Operations (DSO) type in the request is not supported by the server.
DNS 22: Bad truncation. The TSIG record was truncated in a way that makes it impossible to verify the message signature.
You encounter 11 when your client attempted a DSO operation (like a keepalive or push subscription) that the server does not recognize or has not implemented.
You encounter 22 when a large DNS response was truncated (TC bit set) but the TSIG MAC was computed over the full message, making the truncated version unverifiable.
Когда что использовать
For 11 (DSOTYPENI): Verify that both client and server support the same DSO-TYPE. Upgrade the server software or fall back to traditional DNS queries. For 22 (BADTRUNC): Retry the query over TCP to avoid truncation. If using UDP, ensure your EDNS buffer size is large enough to receive the full signed response.