DNS over TLS: The Protection and Its Boundaries

TLS-protected DNS encrypts queries and responses on the connection between a client and its chosen resolver. It limits what observers on that path can read or alter, provided the client authenticates the resolver. The resolver still sees the requests, and other parts of a connection can reveal information about the destination.

What happens to a query

A device looking up an address sends a DNS request to a recursive resolver. With DNS over TLS, the client establishes a TLS session to that resolver, conventionally using TCP port 853, and carries DNS messages inside the encrypted connection. The resolver answers from its cache when it has a usable record, or obtains an answer through its configured resolution path.

The protection applies to that client-to-resolver session. A local network observer can generally still see the resolver’s IP address, timing and traffic volume. Subsequent connections to a destination expose its IP address to networks carrying that traffic; other protocol metadata may also reveal a hostname. The resolver can see query contents and apply its own logging, filtering or retention policies. Its onward queries have their own transport and privacy properties.

DNS over TLS also serves a different purpose from DNSSEC. TLS protects a particular connection; DNSSEC validation checks signed DNS data where a chain of trust is available. An organization can use both where supported.

Configure identity and failure behavior

For authenticated operation, configure the resolver address and the expected authentication name according to the client or gateway documentation. The client checks that the certificate is valid, chains to a trusted authority and matches the expected name. A wrong name, expired certificate or missing trust anchor can prevent the connection. Resolver selection should also account for its access policy and whether it can answer the organization’s internal names.

Decide how the client behaves if it cannot establish the encrypted session. A strict configuration can fail resolution rather than fall back to unencrypted DNS; an opportunistic configuration may permit fallback, depending on the implementation. The latter can preserve connectivity but changes the privacy properties of the lookup. Test a blocked port, an unavailable resolver and an invalid certificate so support staff know which failure users will see. A second authenticated resolver can improve availability if it supplies the same required answers and policy.

A client using TLS-secured DNS or a local gateway may cache responses, so a repeated lookup can succeed without a new query reaching the remote resolver. Cached data remains usable according to its lifetime and implementation. When testing DNS encryption with TLS, clear or account for caches and inspect the actual connection; a successful lookup alone does not prove the remote session was encrypted.

HTTPS transport and private names

DNS over HTTPS sends DNS messages in HTTP exchanges protected by TLS, rather than the dedicated transport on port 853. Both can protect the client-to-resolver path, but use different endpoints and integration methods. RFC 8484 describes the HTTPS exchange; the resolver selected and its policies still matter.

A private zone is a set of DNS records made available within an organization’s intended scope. Encryption does not make a public resolver aware of those records. A device using encrypted DNS through TLS may need an internal resolver, a VPN, or conditional forwarding for internal domains. Test both an internal name and a public name from the locations where staff work, including after connecting to the VPN.

Should every device use the same resolver?

Only if that resolver meets each device’s operational needs. A managed internal resolver can serve private names and enforce organizational policy, while a public resolver may suit devices that need only public names. For either choice, verify authenticated transport, access to required zones and the selected behavior during an outage before deploying the TLS connection for DNS across the fleet.