DNS 11 DSOTYPENI vs 18 BADTIME
Both DNS 11 (DSOTYPENI) and 18 (BADTIME) 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, 18 means that signature out of time window. The TSIG signature timestamp is outside the allowed clock skew, indicating a time synchronization issue.
설명
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.
설명
Signature out of time window. The TSIG signature timestamp is outside the allowed clock skew, indicating a time synchronization issue.
이 코드를 보게 되는 경우
The clocks on the DNS client and server are too far apart (usually more than 5 minutes), causing TSIG signature validation to fail.
해결 방법
Synchronize clocks on both machines using NTP. Check that the TSIG fudge value (allowed skew) is reasonable — the default 300 seconds is usually sufficient.
주요 차이점
DNS 11: DSO-TYPE Not Implemented. The DNS Stateful Operations (DSO) type in the request is not supported by the server.
DNS 18: Signature out of time window. The TSIG signature timestamp is outside the allowed clock skew, indicating a time synchronization issue.
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 18 when the clocks on the DNS client and server are too far apart (usually more than 5 minutes), causing TSIG signature validation to fail.
언제 어떤 것을 사용할지
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 18 (BADTIME): Synchronize clocks on both machines using NTP. Check that the TSIG fudge value (allowed skew) is reasonable — the default 300 seconds is usually sufficient.