All articles

DNS Infrastructure

DNS over HTTPS and DNS over TLS: What They Protect, and What They Don't

Encrypted DNS protects the connection to your resolver, but it doesn't make every part of a lookup private or replace DNSSEC. Here's how DoH and DoT work, and why your browser may see a different answer from your terminal.

November 12, 2026

You enable “secure DNS” in your browser and expect every DNS lookup on the computer to become encrypted. Later, the browser reaches a site that a terminal lookup can't find.

Both results can make sense. Encrypted DNS describes how a query travels to a resolver. The application choosing that resolver, the network policy, and the rest of the lookup still matter.

The connection being protected

Ordinary DNS commonly uses UDP or TCP on port 53 without encryption. An observer on that path can potentially read the queries and responses.

DNS over TLS and DNS over HTTPS protect the connection between a client and its chosen recursive resolver. The client might be a browser, an operating system, or a local forwarding resolver.

It doesn't cover the next hop. When your resolver doesn't have an answer cached, it asks root, TLD, and authoritative nameservers for it, and those queries almost always travel as ordinary unencrypted DNS. Encrypted DNS protects the segment between you and your resolver, not the whole lookup.

The DNS basics guide describes the participants in that lookup.

DNS over TLS

DNS over TLS, usually shortened to DoT, carries DNS messages inside a TLS connection. Its standard port is 853. The protocol is defined in RFC 7858.

The client needs a way to authenticate the resolver it connects to. Simply encrypting traffic to an unverified endpoint is not the same as knowing that endpoint is the resolver you intended.

A dedicated port makes DoT recognizable to network administrators. Networks can allow or restrict it explicitly, which affects whether a configured client can use it.

DNS over HTTPS

DNS over HTTPS, or DoH, carries DNS messages using HTTPS requests to a resolver endpoint. RFC 8484 defines the protocol.

DoH commonly uses port 443, the same port used by HTTPS websites. A browser can make these requests itself instead of asking the operating system to resolve every hostname.

That gives an application a way to select its own DNS service, but it can also make DNS behavior less obvious when troubleshooting. The resolver in your browser settings may differ from the one your operating system received from Wi-Fi, a VPN, or a corporate network.

Neither protocol says that every client must use the same provider or fallback behavior. Check the application's actual configuration.

What encryption doesn't hide

The chosen recursive resolver still processes your query. Encrypted transport changes who can observe the path; it doesn't remove the resolver from the trust relationship.

DNS encryption also doesn't hide where you go next. Anyone watching the network can still see the IP address you connect to, and in most cases the site's hostname, which is sent unencrypted at the start of the TLS connection (the SNI field) unless both browser and site support Encrypted Client Hello.

The IETF's DNS privacy considerations discuss the different parties that can observe information during resolution. For a practical decision, ask who runs the resolver, what its policies are, and whether it fits your network requirements.

Why this doesn't replace DNSSEC

DNSSEC and encrypted transport address different parts of the problem.

DNSSEC provides signatures that let a validating resolver check authenticated DNS data. DoH and DoT protect a transport connection to a resolver.

You can use both. An encrypted connection can carry a DNSSEC validation failure, and a validating resolver can serve clients over ordinary DNS. Encryption alone doesn't prove that a published address is the one a domain owner intended.

Why the browser and terminal can disagree

Consider a company that serves an internal address for portal.example.com through its VPN resolver. A browser using an independently configured public DoH resolver may see the public answer instead, unless browser or network policy handles that name differently.

Other differences can come from separate caches or filtering policies. The symptom doesn't by itself prove that encrypted DNS is broken.

A useful investigation is:

  1. Note the browser's secure-DNS setting and chosen provider.
  2. Identify the operating system or VPN resolver.
  3. Query that resolver and a public resolver explicitly.
  4. Compare the results with the view the application is supposed to receive.

For example:

dig @1.1.1.1 portal.example.com A
dig @8.8.8.8 portal.example.com A

These commands compare ordinary DNS answers from named public resolvers. They don't test DoH just because the providers also offer encrypted endpoints. To query over an encrypted transport, dig 9.18 or newer supports +https and +tls (the version bundled with macOS is older):

dig @1.1.1.1 portal.example.com A +https
dig @1.1.1.1 portal.example.com A +tls

The split-horizon DNS article covers intentional differences between internal and public views.

How DNS monitoring fits in

DoH, DoT, and DNSSEC all protect answers on their way to you. None of them can tell whether the answer is the one you meant to publish. If someone gets into your DNS provider or registrar account and changes your MX or A record, DNSSEC signs the new record and DoH delivers it, privately and intact.

That's the gap change monitoring fills. OneDollarDNS checks your records at the source, your authoritative nameservers, and alerts you when a value changes, whoever made the change and whatever transport your users happen to use.

It doesn't reproduce every browser's resolver choice or internal network view. When users see different results, compare their resolution paths as well as the record history. An unchanged authoritative answer can coexist with different cached or policy-filtered answers at the clients.

Monitor your DNS for $1/domain/month

OneDollarDNS watches your DNS records and alerts you when anything changes.

Get started free