DNS 7 YXRRSET vs 9 NOTAUTH
Both DNS 7 (YXRRSET) and 9 (NOTAUTH) 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, 9 means that server Not Authoritative for zone, or Not Authorized. The server is not authoritative for the zone named in the Zone section.
설명
RR Set Exists when it should not. A resource record set exists that the update prerequisite says should not.
이 코드를 보게 되는 경우
A DNS UPDATE failed because a specific RRset (e.g., an A record) already exists when the prerequisite required it to be absent.
해결 방법
Delete the conflicting RRset before retrying the update, or adjust your prerequisite conditions to match the actual zone state.
설명
Server Not Authoritative for zone, or Not Authorized. The server is not authoritative for the zone named in the Zone section.
이 코드를 보게 되는 경우
You sent a dynamic update or zone operation to a server that is not the authoritative master for that zone, or the server rejected it due to TSIG authentication failure.
해결 방법
Send the update to the correct primary authoritative server for the zone. If using TSIG, verify the key name and secret match on both client and server.
주요 차이점
DNS 7: RR Set Exists when it should not. A resource record set exists that the update prerequisite says should not.
DNS 9: Server Not Authoritative for zone, or Not Authorized. The server is not authoritative for the zone named in the Zone section.
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 9 when you sent a dynamic update or zone operation to a server that is not the authoritative master for that zone, or the server rejected it due to TSIG authentication failure.
언제 어떤 것을 사용할지
For 7 (YXRRSET): Delete the conflicting RRset before retrying the update, or adjust your prerequisite conditions to match the actual zone state. For 9 (NOTAUTH): Send the update to the correct primary authoritative server for the zone. If using TSIG, verify the key name and secret match on both client and server.