DNS 7 YXRRSET vs 16 BADVERS/BADSIG
Both DNS 7 (YXRRSET) and 16 (BADVERS/BADSIG) belong to the DNS Response Codes (RCODEs) category. 7 indicates that rR Set Exists when it should not. A resource record set exists that the update prerequisite says should not. Meanwhile, 16 means that bad OPT Version or TSIG Signature Failure. Either the EDNS version in the OPT record is not supported, or the TSIG signature on the message failed verification.
Beschreibung
RR Set Exists when it should not. A resource record set exists that the update prerequisite says should not.
Wann Sie es sehen
A DNS UPDATE failed because a specific RRset (e.g., an A record) already exists when the prerequisite required it to be absent.
Wie man es behebt
Delete the conflicting RRset before retrying the update, or adjust your prerequisite conditions to match the actual zone state.
Beschreibung
Bad OPT Version or TSIG Signature Failure. Either the EDNS version in the OPT record is not supported, or the TSIG signature on the message failed verification.
Wann Sie es sehen
As BADVERS: your client sent an EDNS version higher than the server supports. As BADSIG: the TSIG MAC on the message did not match, indicating a shared-secret mismatch or message tampering.
Wie man es behebt
For BADVERS, downgrade the EDNS version (most servers support version 0 only). For BADSIG, regenerate and re-synchronize the TSIG shared secret on both endpoints.
Wesentliche Unterschiede
DNS 7: RR Set Exists when it should not. A resource record set exists that the update prerequisite says should not.
DNS 16: Bad OPT Version or TSIG Signature Failure. Either the EDNS version in the OPT record is not supported, or the TSIG signature on the message failed verification.
You encounter 7 when a DNS UPDATE failed because a specific RRset (e.g., an A record) already exists when the prerequisite required it to be absent.
You encounter 16 when as BADVERS: your client sent an EDNS version higher than the server supports. As BADSIG: the TSIG MAC on the message did not match, indicating a shared-secret mismatch or message tampering.
Wann welchen verwenden
For 7 (YXRRSET): Delete the conflicting RRset before retrying the update, or adjust your prerequisite conditions to match the actual zone state. For 16 (BADVERS/BADSIG): For BADVERS, downgrade the EDNS version (most servers support version 0 only). For BADSIG, regenerate and re-synchronize the TSIG shared secret on both endpoints.