Oblivious DNS over HTTPS separates the address from the query
Oblivious DNS over HTTPS separates the address from the query DNS over HTTPS protects a DNS query between a client and a resolver, but a resolver that receives a query over a TLS connection can still associate the quer
Oblivious DNS over HTTPS separates the address from the query
DNS over HTTPS protects a DNS query between a client and a resolver, but a resolver that receives a query over a TLS connection can still associate the query with the client's network address. Oblivious DNS over HTTPS adds an application-layer split. A proxy sees the client address and an encrypted query. A target sees the query and encrypted response without receiving the client address. The design reduces direct correlation at either single server, not at every observer in every situation.
RFC 9230 uses HPKE to encrypt DNS messages and defines a configuration that identifies the key material and supported parameters. The client encrypts a query for the target, sends it through the proxy, and receives an encrypted response. The proxy forwards the envelope. The target decrypts the query and encrypts the answer without needing the client's address for the cryptographic operation.
Unlinkability has a threat model
Timing, message size, repeated queries, and proxy logs can still create correlation points. A proxy and target that share operational control may also be able to combine records outside the protocol. The design does not make DNS query content harmless. A query for a sensitive internal hostname can still reveal intent to the target.
The proxy must be selected as a trust component, not as an anonymous checkbox. Its retention policy, jurisdiction, authentication method, and relationship to the target matter. Organizations should document which party can see the network address, which party can see the query, and whether a service provider can change the configuration without an owner review.
Configuration and key lifecycle
The target publishes an ODoH configuration with a key identifier and public key material. Clients must validate the configuration over an authenticated channel and use the key identifier when constructing the envelope. A configuration that changes without a client update can break availability. A client that accepts any returned configuration can lose the property it intended to deploy.
Operators should rotate keys with overlap, publish an explicit retirement plan, and monitor failures by configuration version without logging query contents. A proxy should set request size limits, timeouts, and rate limits. A target should return only the encrypted response required by the protocol and avoid keeping raw query records longer than the service policy requires.
What DNSSEC still does
ODoH protects the query path. It does not validate the answer. DNSSEC, local policy, or another authenticated resolution path still has to establish whether the answer is authoritative and unmodified. A deployment that confuses privacy with integrity can hide the query from the network while accepting a forged result.
Start a review by drawing the three parties: client, proxy, and target. Mark which fields each party can observe and which logs each party retains. Then test configuration failure, key rotation, malformed envelopes, replay-like repeats, and a target that returns an invalid response. The result is a clearer privacy claim and a smaller set of assumptions.
References
[1] RFC 9230, Oblivious DNS over HTTPS. https://www.rfc-editor.org/rfc/rfc9230.html
[2] RFC 8484, DNS Queries over HTTPS. https://www.rfc-editor.org/rfc/rfc8484.html
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.