System-wide

Windows Setup

Windows can use DNS over HTTPS, but custom providers usually need one extra step before they appear as encrypted options in the settings UI. Once the template is registered, setup is straightforward.

At a glance

Best for

Windows 11 users who want encrypted DNS for the whole system.

Protocol

DoH

Coverage

System-wide

Setup time

4 to 6 minutes

Main input

https://dns.easyhns.com/dns-query

Windows Setup stays focused on the shortest accurate path for this platform.

Guide summary

Windows 11 users who want encrypted DNS for the whole system.DoHSystem-wideModerate4 to 6 minutes

Important

The Windows DoH dropdown only appears for resolvers the system knows how to map to a DoH template. That is why the PowerShell registration step matters.

Before you start

Check 01

Windows 11 or a recent Windows build with DNS over HTTPS support.

Check 02

Administrator access for the PowerShell step.

Exact Values

Use the right field for the right input.

URL fields need the full DoH URL. Hostname fields need the DoT hostname only. IP fields need the raw address only.

DoH template

https://dns.easyhns.com/dns-query

Register this with Windows so it knows how to use Easy HNS securely.

IPv4 server

51.24.7.1

Set this as your preferred DNS server.

IPv6 server

2a05:d01c:b4a:2900:945c:1a85:e537:cf80

Optional, but useful on IPv6-capable networks.

Step-by-Step

Short steps, no filler.

Follow the route in order, then verify the active DNS setting before changing another layer.

Step 01

Register Easy HNS as a known DoH server

Open Windows Terminal or PowerShell as Administrator and run: Add-DnsClientDohServerAddress -ServerAddress '51.24.7.1' -DohTemplate 'https://dns.easyhns.com/dns-query' -AllowFallbackToUdp $False -AutoUpgrade $True. If you use IPv6, repeat the command with 2a05:d01c:b4a:2900:945c:1a85:e537:cf80.

Step 02

Open the active network adapter settings

Go to Settings > Network & internet, open your active Wi-Fi or Ethernet connection, then open its details page.

Step 03

Edit DNS assignment manually

Find DNS server assignment, choose Edit, switch the mode to Manual, turn on IPv4, and enter the Easy HNS IPv4 address. If the encryption dropdown is available, set it to Encrypted only (DNS over HTTPS).

Step 04

Optionally add IPv6 too

If your network supports IPv6, turn on IPv6 and add 2a05:d01c:b4a:2900:945c:1a85:e537:cf80. Use the encrypted setting there as well, then save.

How to verify

Check 01

After saving, disconnect and reconnect the network once if the adapter keeps old DNS state.

Check 02

Visit a Handshake domain in your browser. If it resolves without a browser-specific DNS override, Windows is using Easy HNS system-wide.

Check 03

If the encryption dropdown never appears, rerun the PowerShell registration command and reopen Settings.

Troubleshooting

Note 01

If Windows says the cmdlet is unknown, install current system updates first. Older builds may not expose the newer DNS client tooling.

Note 02

If the encrypted dropdown stays greyed out, check that the IP address in PowerShell matches the one you enter in Settings exactly.

Note 03

If corporate device policy controls DNS, a browser-specific guide may be the only path you can change yourself.

Important note about Handshake website security warnings

Using Easy HNS gives you convenient access to Handshake domains, but standard browsers may still show security warnings for some Handshake websites.

Why? Because most mainstream browsers do not natively validate Handshake trust and DANE/TLSA in the same way they validate the conventional HTTPS web.

As a result:

  • some Handshake websites may load over HTTP;
  • some may show a browser warning or missing secure indicator;
  • this is often a browser trust-model limitation, not automatically proof that the website is malicious.

If you want a stronger Handshake-native browsing experience with DANE/TLSA support, use Fingertip for desktop.

Using a VPN?

Easy HNS still works well with VPNs, but browser Secure DNS can override router or system DNS, and some VPN apps force their own resolver. Use 51.24.7.1 only in IP fields, use https://dns.easyhns.com/dns-query only in DoH fields, and verify which layer is actually winning.