RFC 9567: DNS Error Reporting
In plain English — editorial summary, not part of the RFC
DNS error reporting is a lightweight reporting mechanism that provides the operator of an authoritative server with reports on DNS resource records that fail to resolve or validate. A domain owner or DNS hosting organization can use these reports to improve domain hosting. The reports are based on extended DNS errors as described in RFC 8914. When a domain name fails to resolve or validate due to a misconfiguration or an attack, the operator of the authoritative server may be unaware of this. To mitigate this lack of feedback, this document describes a method for a validating resolver to automatically signal an error to a monitoring agent specified by the authoritative server. The error is encoded in the QNAME; thus, the very act of sending the query is to report the error.
Document record
- Document ID
- RFC9567
- Published
- April 2024
- Authors
- R. Arends; M. Larson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 11
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9506Explicit Host-to-Network Flow Measurements TechniquesCurrent
October 2023
- RFC 9342Clustered Alternate-Marking MethodCurrent
December 2022
- RFC 6632An Overview of the IETF Network Management StandardsCurrent
June 2012
- RFC 6022YANG Module for NETCONF MonitoringCurrent
October 2010
- RFC 3144Remote Monitoring MIB Extensions for Interface Parameters MonitoringCurrent
August 2001
- RFC 1513Token Ring Extensions to the Remote Network Monitoring MIBCurrent
September 1993
- RFC 9343IPv6 Application of the Alternate-Marking MethodCurrent
December 2022
- RFC 9987Secure Shell (SSH) Agent ProtocolCurrent
May 2026
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?