Choose the HTTPS resolver endpoint
01A DoH client uses a configured URI template for its chosen resolver.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 3 ↗
RFC 8484 · § 3EXAMPLE
3 / 3
03
Use that endpoint for a DNS exchange.
Use that endpoint for a DNS exchange.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
RFC 1035 DNS transportsRFC 8484 §§ 3–4
DoH adds HTTPS request/response mapping and resolver URI templates while carrying DNS wire messages; it does not replace the DNS data model.
Read the updated RFC section ↗An arbitrary URI learned from an untrusted source is not automatically an authorized resolver.
- An arbitrary URI learned from an untrusted source is not automatically an authorized resolver.
- HTTPS authenticates the selected service; resolver-selection policy remains separate.
The drawing is a simplified worked example. Follow the linked RFC and its updates for implementation requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy