-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've figured out how to get Windows 11 to recognise AdGuard DNS as encryptable, but I don't know which folder/page to add such info to #288
Comments
Yeah, this probably should be a part of the DNS configuration instructions, not the knowledge base. |
I seem to be running on 21H2, which I suppose explains the difference. But thanks for the headsup. Good to know the settings will get more expanded for stable users in 4 months or so. |
We'll have to postpone this until the update is out then. |
I still feel the OP stuff is worth mentioning, since seemingly no relevant search results on Google seem to demonstrate any such registry fix, thus AdGuard would've shared new info with the world. |
Added at v2.4 update |
The instruction |
Windows 11's "Network and Internet" settings added an option to set DNS servers as encrypted. But by default, they only made it possible to turn on for the IP addresses used by Google DNS, CloudFlare DNS, and Quad9, which can be displayed with
netsh dns show encryption
in PowerShell. I have however figured out how to get it to recognise public AdGuard DNS IPs too.The .reg file content that would've enabled it, from what I can tell:
What the settings menu looks like, complete with
94.140.14.140
having encryption turned on, which can't be done on stock Windows 11 stable installations (In this case, it was accomplished with direct registry editing instead of a .reg file. I can take a UK English screenshot on request):Ideally, this kind of info would've been suited for https://adguard-dns.io/en/public-dns.html → "Method 2: Configure AdGuard DNS manually" → Windows 11; but it doesn't seem to be part of the main Knowledge Base at the time of writing, nor are there any pages in the actual Knowledge Base that are anywhere nearly as suited for it.
The text was updated successfully, but these errors were encountered: