DNS over HTTPS vs DNSSEC: Privacy and Validation
Encrypted DNS and DNSSEC are often grouped under DNS security, but they protect different things. DoH and DoT protect a client-to-resolver connection; DNSSEC helps validate signed DNS data.
By Protocol Explorer · Updated
First identify the DNS path and the party you trust
A stub resolver asks a recursive resolver, which may answer from cache or query authoritative servers. Traditional DNS often exposes the query on the client-to-resolver path. DoH or DoT can encrypt that path, but the selected resolver receives the question in order to answer it.
The privacy question is therefore not simply whether DNS is encrypted. Ask which network observers are prevented from reading the query, which resolver can see it, whether the resolver logs it, and whether the answer is validated.
DNS over HTTPS maps DNS messages into HTTP
RFC 8484 maps each DNS query-response pair into an HTTP exchange using the application/dns-message media type. The client connects to a configured HTTPS resolver. GET can encode the DNS message in a base64url query parameter; POST can carry it in the request body.
TLS protects the request from on-path observers and helps authenticate the HTTPS server. The resolver still sees the query after terminating TLS. A 200 HTTP status can carry a DNS response such as NXDOMAIN; HTTP status and DNS response code describe different layers.
DNS over TLS encrypts the resolver connection too
RFC 7858 defines DNS over TLS as DNS messages carried over a TLS connection to a configured resolver. It provides a dedicated DNS transport rather than mapping each query into HTTP. Both DoT and DoH can reduce visibility to an on-path observer, subject to metadata and endpoint configuration.
Choosing either service changes which resolver handles the request. Split-horizon policy, filtering and location can produce different answers. Encrypted DNS does not guarantee identical results across providers.
DNSSEC validates data rather than hiding the query
DNSSEC uses signatures and a chain of trust to help a validating resolver or client determine whether signed DNS data is authentic and unmodified. DS records connect a child zone’s key to its parent; DNSKEY and RRSIG records support verification.
DNSSEC does not encrypt the question name. A DNSSEC-signed query sent over plaintext DNS can still be visible on the path. Conversely, a DoH response can be encrypted in transit while the resolver returns data that the client has not independently validated.
The protections can be used together
A client can use DoH or DoT to protect the path to its chosen resolver while the resolver performs DNSSEC validation. Some clients can validate DNSSEC themselves. The assurance depends on where validation happens and whether the client trusts that party’s result.
For a policy or incident review, record the resolver, transport, validation location and trust anchor. Saying only encrypted DNS or DNSSEC enabled leaves out the boundary that matters.
Diagnose transport errors separately from validation errors
A TLS certificate or connection failure occurs before the client receives a DNS answer. An HTTP 415 or 401 from a DoH endpoint is an HTTP-layer problem. A DNS SERVFAIL may be a resolver failure or a DNSSEC validation result. Read the outer status and inner DNS message separately.
At a network-side capture without session keys, DoH and DoT queries are not visible as ordinary DNS messages. Use authorized resolver logs or endpoint diagnostics and state whether the data was decrypted or obtained from a client API.
Managed resolver policy and bootstrap
Managed networks can depend on a local resolver for split DNS, internal host names, filtering or policy. A browser or operating system that independently selects a public encrypted resolver may produce different answers or bypass an intended control. Check the effective resolver configuration and any enterprise policy before interpreting a DoH connection as an application defect.
The DoH endpoint itself also needs an address before the client can establish HTTPS. Implementations therefore need a bootstrap path that does not depend on an unavailable resolver, and they need a fallback policy for endpoint failure. These details explain why a browser setting alone may not describe the resolver used by every application on the device.
Choose a control based on the requirement
If the goal is to prevent local-path observers from reading queries, use an encrypted DNS transport with a resolver whose privacy policy is acceptable. If the goal is to detect forged or modified signed DNS data, enable validation and monitor DNSSEC errors. Neither control eliminates the need to evaluate resolver trust and application security.
The lesson pages for DNS over HTTPS, DNSSEC and DNS walk through each exchange separately.