RFC 9606: DNS Resolver Information
In plain English — editorial summary, not part of the RFC
This document specifies a method for DNS resolvers to publish information about themselves. DNS clients can use the resolver information to identify the capabilities of DNS resolvers. How DNS clients use such information is beyond the scope of this document.
Document record
- Document ID
- RFC9606
- Published
- June 2024
- Authors
- T. Reddy.K; M. Boucadair
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
- RFC 9602Segment Routing over IPv6 (SRv6) Segment Identifiers in the IPv6 Addressing ArchitectureCurrent
October 2024
- RFC 9631The IPv6 Compact Routing Header (CRH)Current
August 2024
- RFC 9575DRIP Entity Tag (DET) Authentication Formats and Protocols for Broadcast Remote Identification (RID)Current
June 2024
- RFC 9664An EDNS(0) Option to Negotiate Leases on DNS UpdatesCurrent
June 2025
- RFC 9665Service Registration Protocol for DNS-Based Service DiscoveryCurrent
June 2025
- RFC 9669BPF Instruction Set Architecture (ISA)Current
October 2024
- RFC 9542IANA Considerations and IETF Protocol and Documentation Usage for IEEE 802 ParametersCurrent
April 2024
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?