Join our Newsletter — 33% off our NHI Course
Home› Guides› Encrypted DNS Enterprise Guide: Control DoH, DoT and…
Guide Network Security

Encrypted DNS Enterprise Guide: Control DoH, DoT and DoQ Without Losing Visibility

PDF for newsletter subscribers · free to read online

← All guides
By NHI Mgmt Group, edited by Lalit Choda Updated 27 October 2026 13 min read
On this page

Encrypted DNS protects queries from eavesdroppers on the network, but when browsers, applications or malware send DNS over HTTPS straight to a public resolver, the enterprise loses its DNS logging, protective DNS filtering and split-horizon resolution in one move. DNS over TLS (DoT), DNS over HTTPS (DoH) and DNS over QUIC (DoQ) are all IETF standards, and every major browser and operating system now supports at least one of them. The question for security teams is not whether to allow encryption, but where it terminates. This guide explains the three protocols, how clients discover encrypted resolvers, the browser and Windows policy settings that keep clients on your resolver, how to detect bypass, and a phased plan to encrypt DNS end to end without going blind. It is for network security, endpoint and SOC teams.

Key takeaways

  • Encrypt to your own resolver, not around it. The target state is clients using DoH or DoT to an enterprise or contracted protective resolver, with that resolver doing logging, filtering and DNSSEC validation.
  • DoT and DoQ are easy to spot; DoH is not. DoT and DoQ use port 853 by default; DoH rides on port 443 and is designed to blend with ordinary HTTPS, so control relies on policy and known-resolver blocking.
  • Policy beats blocking. Set Chrome DnsOverHttpsMode, the Firefox DNSOverHTTPS policy and the Windows "Configure DNS over HTTPS (DoH) name resolution" setting explicitly on managed devices.
  • Discovery standards now exist. DDR (RFC 9462) and DNR (RFC 9463) let your network advertise its own encrypted resolver so clients upgrade to it instead of a public one.
  • Do not require DoH on domain-joined Windows yet. Microsoft warns that the Windows Server DNS service does not support DoH queries and that Active Directory depends heavily on DNS.

The three encrypted DNS protocols

PropertyDNS over TLS (DoT)DNS over HTTPS (DoH)DNS over QUIC (DoQ)
StandardRFC 7858, Standards Track, May 2016RFC 8484, Standards Track, October 2018RFC 9250, Standards Track, May 2022
Transport and portTCP 853 by default; an alternative port must not be 53HTTPS (HTTP/2 minimum recommended), normally port 443UDP 853 by default, ALPN token doq; must not use UDP 53
Message formatDNS wire format with TCP length prefixapplication/dns-message, via GET with a base64url dns parameter or POSTDNS wire format, one query per QUIC stream, message ID set to 0
Server authenticationOpportunistic profile, or out-of-band SPKI pinning profileStandard HTTPS certificate validation against a configured URI templateTLS 1.3 within QUIC
Visibility to network defendersConnection to port 853 is visible; content is notLooks like any HTTPS session to the resolver's hostUDP 853 visible; content is not
ScopeMainly stub to recursiveStub to recursive, often built into browsers and appsStub to recursive, recursive to authoritative, and zone transfers
  • Why DoH is the hard case: RFC 8484 notes that using port 443 helps DoH traffic mix with other HTTPS traffic, which makes interference and traffic analysis harder. That is a privacy feature on hostile networks and a visibility problem on yours.
  • Integrity: RFC 8484 also notes that HTTPS protects the channel but does not provide DNSSEC-level data integrity. Encryption to a resolver tells you nothing about whether the resolver's answer is authentic; keep DNSSEC validation on the resolver.
  • Bootstrapping: a DoH client needs to resolve the DoH server's own name without DoH, which is why policy templates often include the resolver IP address.

For background on how DNS resolution works underneath these transports, see the DNS Protocol Fundamentals for Defenders Guide.

Why uncontrolled DoH is an enterprise risk

  • Loss of protective DNS: queries sent to a public resolver skip your response policy zones and protective DNS service, so malicious domain blocking stops working for that client. See the Protective DNS Guide.
  • Loss of logging: resolver logs, which tie domains to internal clients, no longer see the queries. DNS-based detection of command and control, DGA and tunnelling goes blind for those clients.
  • Broken internal resolution: split-horizon names and Active Directory records are not in public DNS, so applications fail or leak internal names to an external provider.
  • Malware command and control: malware can use DoH to public resolvers as a covert lookup or tunnel channel that resembles web traffic. This maps to ATT&CK T1071.004 Application Layer Protocol: DNS and T1572 Protocol Tunneling, carried over T1071.001 Web Protocols.
  • Data residency and third-party exposure: every domain a user visits is disclosed to whichever public resolver the application chose, under that provider's terms.

How clients choose an encrypted resolver

Clients pick encrypted resolvers in four ways, and you need a control for each.

MechanismHow it worksEnterprise control
Explicit configurationUser, admin or application sets a DoH template or DoT hostEndpoint and browser policy; lock settings
Same-provider auto-upgradeBrowser or OS upgrades to DoH when the configured system resolver is a known DoH provider (for example Windows' built-in list includes Cloudflare, Google and Quad9 addresses)Point clients at your own resolver; this mechanism then has nothing to upgrade to unless you offer DoH
DDR (RFC 9462, November 2023)Client sends an SVCB query for _dns.resolver.arpa to its unencrypted resolver, which answers with its designated encrypted resolvers. Verified discovery requires the resolver certificate's subjectAltName to include the IP address of the unencrypted resolverAnswer DDR queries on your resolvers to advertise your own DoH or DoT endpoint, or return NODATA to advertise none
DNR (RFC 9463, November 2023)Network advertises the encrypted resolver via DHCPv4 option 162 (OPTION_V4_DNR), DHCPv6 option 144 (OPTION_V6_DNR) or the IPv6 RA Encrypted DNS option, with an authentication domain name and SvcParamsConfigure on DHCP servers and routers; RFC 9463 says DNR takes precedence over DDR

The Firefox canary domain

Mozilla documents a canary domain, use-application-dns.net, that networks can use to tell Firefox not to enable DoH by default. Firefox resolves it through the operating system resolver; any response other than NOERROR with A or AAAA records (for example NXDOMAIN) disables default DoH. Mozilla states that it does not apply to users who turned DoH on themselves, so treat it as a helper for unmanaged devices on your network, not a control. On managed devices use enterprise policy.

Policy settings for managed endpoints

PlatformSettingValues and notes
Google Chrome and Chromium-based browsersDnsOverHttpsMode, with DnsOverHttpsTemplates for the resolver URIoff, automatic (DoH first, may fall back to insecure DNS on error) or secure (DoH only, fails on error). Chromium's policy definition states that if the policy is unset, managed devices do not send DoH queries
Mozilla FirefoxDNSOverHTTPS policy (keys Enabled, ProviderURL, Locked, ExcludedDomains, Fallback)Set Locked so users cannot change it; ExcludedDomains keeps internal namespaces on system DNS; Fallback added in Firefox 124
Windows (client and Windows Server 2022 onwards)Group Policy: Computer Configuration\Policies\Administrative Templates\Network\DNS Client\Configure DNS over HTTPS (DoH) name resolutionAllow DoH, Prohibit DoH or Require DoH. PowerShell Add-DnsClientDohServerAddress registers a resolver template, with -AllowFallbackToUdp $False to block cleartext fallback

Decision guidance: where your resolver offers DoH, set browsers to secure with your template, and Windows to Allow DoH with your resolver registered. Where it does not yet, set browsers to off so they use the system resolver, and plan the resolver upgrade. Microsoft advises against Require DoH on domain-joined computers because the Windows Server DNS service does not accept DoH and AD DS depends on DNS; it suggests IPsec connection security rules if you need to protect that traffic. A small organisation without its own resolvers can achieve the same outcome by contracting a protective DNS service that offers DoH with per-organisation logging and setting it as the only allowed template.

Network controls and bypass detection

Policy covers managed browsers and operating systems. It does not cover unmanaged devices, applications with hard-coded resolvers, or malware. Network controls catch the rest.

  • Block outbound DoT and DoQ: deny TCP and UDP 853 from all internal addresses except your resolvers. This is a simple, low false positive control.
  • Block outbound Do53 except from resolvers: deny UDP and TCP 53 to the internet from clients, so legacy and fallback traffic is forced through your resolver.
  • Block known public DoH endpoints: use your secure web gateway or firewall category for DoH services, or maintained lists of DoH resolver host names and addresses, and block them by name (via SNI and protective DNS) and by IP. Expect lists to be incomplete.
  • Answer resolver bootstrap names locally: return NXDOMAIN or a sinkhole for public DoH host names on your resolver, which stops clients that resolve the DoH host through system DNS.
  • TLS inspection, where lawful and proportionate: inspection can classify application/dns-message traffic, but adds risk and complexity. See the TLS Inspection Guide.
DetectionData sourceWhat it indicates
Connections to TCP or UDP 853 from non-resolversFirewall and flow logsDoT or DoQ bypass by an app, user or malware
TLS connections whose SNI or destination matches public DoH servicesProxy, firewall, secure web gatewayDoH bypass; correlate with process on the endpoint
Hosts with web traffic but almost no resolver queriesResolver logs joined to proxy logsThe host resolves somewhere else
Endpoint process making many small HTTPS requests to a single resolver hostEDR network telemetryPossible DoH tunnel or C2 lookups
Queries for use-application-dns.net and _dns.resolver.arpaResolver logsClients probing for encrypted DNS: useful for inventory
Policy driftEndpoint management compliance reportsBrowsers or Windows hosts without the expected DoH settings

Metrics:

  • Percentage of managed endpoints with browser and OS DoH policy set and locked.
  • Percentage of client DNS queries arriving at enterprise or contracted resolvers (versus estimated total from proxy and flow data).
  • Count of hosts connecting to port 853 or known public DoH endpoints per week, trending to zero.
  • Percentage of client-to-resolver DNS that is encrypted, once your resolver offers DoH or DoT.
  • Mean time to investigate a resolver-bypass alert.

Requirements for your own encrypted resolver

  • Certificates: for DDR verified discovery, the resolver certificate's subjectAltName must include the IP address clients use for unencrypted DNS (RFC 9462). Track expiry like any other production TLS service; an expired resolver certificate breaks name resolution for every client in secure mode.
  • Logging parity: encrypted listeners must write the same query and response logs as port 53, with the client address preserved through any load balancer.
  • Availability: clients configured without fallback depend entirely on the DoH or DoT service. Run it on at least two sites and monitor handshake success and latency, not only port reachability.
  • Cache behaviour: RFC 8484 requires the HTTP freshness lifetime on DoH GET responses not to exceed the smallest TTL in the answer, so intermediate HTTP caches do not extend DNS answers.
  • Revocation lookups: RFC 8484 advises DoH servers not to rely on DNS-based revocation checks during the handshake, which can deadlock when the client needs DNS to complete them.

Phased rollout

  1. Measure first: for two weeks, log connections to port 853 and to known DoH services, and queries for the canary domain and _dns.resolver.arpa. This tells you which clients and applications already use encrypted DNS.
  2. Set managed policy: deploy browser and Windows settings that keep clients on the system resolver (DnsOverHttpsMode off or your own template; Firefox policy locked; Windows Allow DoH only to registered enterprise resolvers). Pilot with one business unit and watch for internal name resolution failures.
  3. Close the network paths: block outbound 53 and 853 from clients, then block known public DoH services, first in log-only mode on the proxy to find business applications that depend on them.
  4. Offer encrypted DNS yourself: enable DoH or DoT on enterprise or protective DNS resolvers with publicly trusted or enterprise-trusted certificates, keeping logging and DNSSEC validation on.
  5. Advertise it: configure DNR options on DHCP and router advertisements, and answer DDR queries, so clients upgrade to your resolver automatically. Remote and roaming users get the resolver template through endpoint policy or the VPN or SASE client.
  6. Tighten: move browsers to secure mode with your template and disable cleartext fallback on Windows where resolver availability is proven.
  7. Rollback: keep each policy as a separate, reversible setting. If your DoH resolver fails, switching browsers back to off and Windows to Allow (with fallback) restores Do53 resolution through the same resolvers without losing filtering.

Framework mapping

FrameworkReferenceRelevance
NIST SP 800-53 Rev. 5SC-7 Boundary Protection and SC-7(5) Deny by Default, Allow by Exception; SC-8 Transmission Confidentiality and Integrity; SC-21 Secure Name/Address Resolution Service (Recursive or Caching Resolver); CM-7 Least Functionality; SI-4 System MonitoringEgress control of DNS, encryption to the resolver, validating resolvers, disabling unapproved DoH, bypass monitoring
NIST CSF 2.0PR.DS-02 Data-in-transit is protected; DE.CM-01 Networks and network services are monitoredEncryption and visibility together
MITRE ATT&CKT1071.004 Application Layer Protocol: DNS; T1071.001 Web Protocols; T1572 Protocol TunnelingAdversary use of DNS and DoH-style channels
MITRE D3FENDD3-OTF Outbound Traffic Filtering; D3-DNSTA DNS Traffic AnalysisBlocking bypass and analysing resolver data

Common failure patterns

  • Blocking 853 and stopping there: DoT is blocked but browsers simply use DoH on 443. Pair port blocks with browser policy and known-resolver blocking.
  • Leaving Chrome in automatic mode with a public resolver: a misconfigured template sends every lookup to a third party and silently falls back only on error, so filtering appears to work for some users and not others.
  • Require DoH on domain-joined Windows: name resolution for Active Directory fails because the Windows DNS Server service does not accept DoH, causing logon and Group Policy failures.
  • No ExcludedDomains for internal namespaces: Firefox sends internal names to an external DoH provider, which both fails and leaks internal host names.
  • Relying on the canary domain: it only affects Firefox default DoH and is ignored when a user enabled DoH themselves, so it is not a control on managed devices.
  • Encrypting without validating: moving clients to DoH while disabling DNSSEC validation on the resolver trades eavesdropping risk for undetected spoofing upstream.

Practitioner checklist

  • Inventory current encrypted DNS use: port 853 flows, public DoH connections, canary and DDR queries.
  • Set and lock browser DoH policy (Chrome DnsOverHttpsMode and templates, Firefox DNSOverHTTPS with Locked and ExcludedDomains).
  • Configure Windows DoH policy to Allow with enterprise resolvers registered; do not Require on domain-joined hosts.
  • Block outbound 53 and 853 from clients and known public DoH endpoints, with exceptions only for your resolvers.
  • Offer DoH or DoT on enterprise or protective resolvers, keeping logging and DNSSEC validation.
  • Advertise your encrypted resolver with DNR (DHCP and RA) and DDR responses.
  • Alert on resolver bypass and on hosts with web traffic but no resolver queries.
  • Give remote users the same resolver template through endpoint or VPN and SASE client policy.

Standards and references

Related NHI Mgmt Group resources: DNS Security Guide · Protective DNS Guide · DNS Logging and Detection Guide · Encrypted Client Hello Guide · TLS Inspection Guide

PDF for subscribers

Take this guide with you

Every section, table and checklist in one PDF, with links to the sources and related guides. Subscribe to our weekly NHI & AI Identity Journal and we’ll email you a download link.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Researched and written by the NHI Mgmt Group editorial team using AI tools, under the editorial direction of Lalit Choda. Facts are drawn from the sources listed on this page and checked by our automated quality process. Last updated 27 October 2026. Spotted an error? Use our contact page.
NHI Mgmt Group, the independent authority on Non-Human Identity, IAM and Agentic AI security. nhimg.org

PDF Downloads for Newsletter Subscribers

Get the guide

Enter your details and we’ll email you a download link.

The full guide is free to read online. The PDF is a thank you for subscribing.

Fill in all fields marked * and tick the PDF box to continue.