RFC 9462: Discovery of Designated Resolvers
In plain English — editorial summary, not part of the RFC
This document defines Discovery of Designated Resolvers (DDR), a set of mechanisms for DNS clients to use DNS records to discover a resolver's encrypted DNS configuration. An Encrypted DNS Resolver discovered in this manner is referred to as a "Designated Resolver". These mechanisms can be used to move from unencrypted DNS to encrypted DNS when only the IP address of a resolver is known. These mechanisms are designed to be limited to cases where Unencrypted DNS Resolvers and their Designated Resolvers are operated by the same entity or cooperating entities. It can also be used to discover support for encrypted DNS protocols when the name of an Encrypted DNS Resolver is known.
Document record
- Document ID
- RFC9462
- Published
- November 2023
- Authors
- T. Pauly; E. Kinnear; C. A. Wood; P. McManus; T. Jensen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9463DHCP and Router Advertisement Options for the Discovery of Network-designated Resolvers (DNR)Current
November 2023
- RFC 9445RADIUS Extensions for DHCP-Configured ServicesCurrent
August 2023
- RFC 9461Service Binding Mapping for DNS ServersCurrent
November 2023
- RFC 9464Internet Key Exchange Protocol Version 2 (IKEv2) Configuration for Encrypted DNSCurrent
November 2023
- RFC 9539Unilateral Opportunistic Deployment of Encrypted Recursive-to-Authoritative DNSCurrent
February 2024
- RFC 9250DNS over Dedicated QUIC ConnectionsCurrent
May 2022
- RFC 8484DNS Queries over HTTPS (DoH)Current
October 2018
- RFC 9526Simple Provisioning of Public Names for Residential NetworksCurrent
January 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?