Blog Post

Networking Blog
4 MIN READ

DoH is now generally available on Windows DNS Server

JorgeCañas's avatar
JorgeCañas
Icon for Microsoft rankMicrosoft
Jun 11, 2026

Today, we’re excited to announce that DoH support for Windows DNS Server is generally available on Windows Server 2025 for client-to-server DNS traffic.

When we first introduced DNS over HTTPS (DoH) for Windows DNS Server in public preview, we described it as a Zero Trust upgrade to the foundation of enterprise networking. With general availability, organizations can now deploy encrypted and authenticated client-to-resolver DNS traffic directly within their existing on-premises DNS infrastructure. The goal is to help improve privacy, reduce spoofing risk, and advance Zero Trust DNS without requiring a new resolver architecture.

This release helps organizations secure one of the most critical, and traditionally exposed components of modern networks while preserving compatibility with existing enterprise DNS deployments.

Why DNS security matters more than ever

DNS remains at the heart of every network interaction: every application, every service, every workload depends on it. Yet historically, DNS traffic has been transmitted in the clear. This could expose sensitive query and response data to passive monitoring and traffic analysis, man‑in‑the‑middle attacks, and unauthorized inspection of user and system behavior.

As enterprise environments adopt Zero Trust architectures and face evolving regulatory requirements, securing DNS further is no longer optional; it’s foundational.

What DoH brings to Windows DNS Server

DNS over HTTPS changes how DNS traffic is transported. DNS encapsulates DNS queries and responses inside HTTPS, encrypted by TLS. With general availability, Windows DNS Server enables the following capabilities:

Capability

Value for organizations

Encrypted DNS (between client and server)

• DNS queries and responses are encrypted in transit using HTTPS.

• Helps prevent eavesdropping and unauthorized inspection.

• Helps protect DNS data from tampering while in transit.

Authentication

• TLS certificates help clients verify the identity of the DNS server.

• Helps reduce the risk of spoofing and impersonation attacks.

Standards-based interoperability

• Built on the IETF DNS over HTTPS standard, RFC 8484.

• Designed to work with modern RFC 8484-compliant clients, including Windows clients that support encrypted DNS.

Integration with existing infrastructure

• Runs within the Windows DNS Server role; no separate resolver is required.

• Existing DNS resolution behavior remains unchanged.

• Traditional unencrypted DNS can continue alongside DoH where required, supporting incremental adoption.

• Traditional unencrypted DNS is used for DNS server to DNS server communication.

From preview to general availability: What’s changed

In our previews, we worked closely with private and public sector organizations to validate real-world deployments and evaluate the experience.

With general availability, this release is designed for production use and delivers several key benefits: enhanced stability and supportability, clearer deployment guidance, greater operational confidence, and improved alignment with enterprise security best practices and Zero Trust architectures.

This milestone reflects your feedback and validation across diverse enterprise environments.

Advancing towards Zero Trust DNS

DoH on Windows DNS Server isn’t just a feature, it’s part of a broader strategy to enable Zero Trust DNS across the Windows ecosystem.

Windows clients already support encrypted DNS. Now, Windows Server provides the on-premises resolver counterpart, enabling encrypted and authenticated DNS across endpoints and infrastructure.

This unified approach helps organizations establish a consistent security posture for name resolution without requiring external DNS services or an architectural redesign.

For many organizations, including U.S. federal agencies, this model also helps support certain requirements for encrypted DNS protocols between clients and resolvers.

For organizations aligning with U.S. federal guidance such as OMB M-22-09 or NIST Secure DNS Deployment Guide, this release supports encrypted DNS communication between clients and Windows DNS Server using standards-based protocols. While this release focuses on encrypting client-to-resolver communication, support for encrypted communication between Windows DNS Server and upstream DNS resolvers is planned for a future update. Together, these capabilities will help enable fully encrypted DNS resolution paths aligned with aspects of U.S. federal Zero Trust objectives.

What to expect operationally

Enabling DoH on Windows DNS Server introduces encrypted communication for supported clients over HTTPS while preserving compatibility with most existing DNS deployments.

Organizations can expect DoH traffic between DoH clients and Windows DNS Server to be encrypted via TLS, DNS queries to be transported as HTTPS requests, existing DNS functionality to continue operating as expected, and mixed environments, encrypted and traditional DNS, to be supported.

This allows organizations to adopt encrypted DNS incrementally, without disrupting existing workloads.

Getting started

DoH is available on Windows Server 2025 running the June 9, 2026 update  (or newer)...

Recommended deployment flow:

  1. Configure a trusted TLS certificate.
  2. Enable DoH in the DNS Server service.
  3. Configure supported clients to use the secure endpoint.

Consult our documentation for more details: Enable DNS over HTTPS in DNS Server.

Share your feedback and help shape future improvements

In addition to standard support channels, you can also submit feedback directly from Windows Server using Feedback Hub. It provides a streamlined way to report issues, suggest enhancements, and share deployment experiences with the Windows DNS Server product team.

Work toward a more secure foundation

DNS has long been one of the most critical and exposed protocols in enterprise networks. With DoH now generally available in Windows DNS Server, your organization can help secure that foundation further.

Consider bringing encrypted DNS into existing infrastructure today. You can help strengthen your organization’s security posture, better align with modern Zero Trust principles, and help protect sensitive network signals from exposure.

Your DNS Server software just got an upgrade, and now it’s ready for production.

 

Updated Jun 11, 2026
Version 1.0

10 Comments

  • Iwan1996's avatar
    Iwan1996
    Copper Contributor

    Great!

    Does this also enforce DoH at the OS/network level, or can browsers (Chrome, Firefox, Edge) still set their own DoH resolver independently and bypass this entirely?

    • JorgeCañas's avatar
      JorgeCañas
      Icon for Microsoft rankMicrosoft

      The scope of this feature is on the DNS server side: it enables Windows DNS Server to accept, process and respond to DNS-over-HTTPS requests. Whether a browser, operating system or any other application uses a DNS server is determined by that client-side DNS configuration and policies in place.

      We do have a feature in Windows 11 (ie. on the client side) called Zero Trust DNS.  That feature will block connections towards any IP address that has not been discovered through the resolver configured on the operating system settings.  So, when that feature is active, web browsers running on that machine will still be able to query their own DNS servers to resolve IP addresses, but the browsers will be unable to connect to the resolved IP addresses.

  • Great news! Is there anything planned for automated certificate management? Editing the HTTP.SYS listener every time the certificate changes isn't an efficient way of managing this feature. Maybe GPO? Thanks

    • JorgeCañas's avatar
      JorgeCañas
      Icon for Microsoft rankMicrosoft

      Thanks for the feedback. Certificate lifecycle management is definitely an area we've heard about from customers.

      DNS over HTTPS on Windows DNS Server leverages HTTP.sys for the HTTPS endpoint, so certificate binding and management are currently handled outside of DNS itself. We generally don't want DNS Server to become a certificate management solution, but we do want to reduce operational friction for administrators.

      GPO is an interesting option for Windows-centric environments, although many customers run mixed-OS networks, so we're also thinking about the broader management experience. Appreciate the suggestion and the feedback.

      • ChristianSchindler's avatar
        ChristianSchindler
        Brass Contributor

        Thanks for the quick reply! I know that DNS Server is leveraging HTTP.SYS. What about a CMDLet which lets us configure the binding, etc.? Or integration with PowerShell DSC? This would also accommodate mixed-os environments…

  • shyju's avatar
    shyju
    Copper Contributor

    Do I need a publicly trusted SSL/TLS certificate for DoH to work?

    • JorgeCañas's avatar
      JorgeCañas
      Icon for Microsoft rankMicrosoft

      Hi.  No, you can use a self-signed certificate on the DNS Server, and you will need to make sure your DNS clients trust it.