DNS Setup on Windows
Classic via adapter settings or encrypted via DoH.
This guide shows the classic configuration via the network adapter properties and – on Windows 11 – the additional activation of DNS-over-HTTPS.
DNS Server Credentials
IPv4 Addresses
Classic DNS servers for IPv4 configuration.
IPv6 Addresses
Native IPv6 reachability of the resolvers.
DNS-over-HTTPS (DoH)
Endpoints for encrypted resolution over HTTPS.
Contents
Adjust adapter settings
Works on Windows 10 and 11 for LAN and Wi-Fi adapters.
Type "Control Panel" into the start menu and open it.
Click "Network and Internet → Network and Sharing Center".
Click "Change adapter settings" on the left.
Right-click the active adapter and select "Properties".
Select "Internet Protocol Version 4 (TCP/IPv4)" and click "Properties".
Choose "Use the following DNS server addresses" and enter the addresses:
Confirm with "OK". Then disable and re-enable the adapter or reboot the machine.
DNS-over-HTTPS on Windows 11
Windows 11 supports encrypted DNS directly in the system.
Settings → Network & Internet, choose adapter, open Hardware properties and click Edit next to DNS server assignment.
Switch to Manual and enable IPv4.
Enter preferred and alternate DNS servers and select Encrypted only (DNS over HTTPS) for both:
Confirm with Save. Windows now shows "Encrypted" next to the DNS server in the adapter status.
Windows DNS Server – Forwarders
On a Windows Server with the DNS Server role installed, add the Dremaxx resolvers as forwarders. All internal clients will then automatically use your resolvers for recursive queries.
Open Server Manager → Tools → DNS or run dnsmgmt.msc directly.
In the left tree right-click the server name and choose Properties.
Switch to the Forwarders tab and click Edit… at the bottom.
Remove any existing entries and add the Dremaxx addresses as IPv4 forwarders:
Uncheck Use root hints if no forwarders are available so the server does not fall back to its own recursion on failure.
Confirm with OK. Optionally clear the DNS cache: Clear-DnsServerCache. A service restart is not required.
Alternative: PowerShell
Requires an elevated PowerShell on the DNS server.