I tried my NextDNS DoH in AdGuard DNS on AdGuard Desktop and also checked with the available Cloudflare Family, but both didn't block adult sites when I tested. Selecting AdGuard Family blocks adult sites. My NextDNS and Cloudflare blocked adult sites when added to Chrome and the network adapter. Can anyone with AdGuard Desktop check this?
Is AdGuard Destop DNS Protection Working?
- Thread starter rashmi
- Start date
Please provide comments and solutions that are helpful to the author of this topic.
ZeroOne
Level 1
- Mar 8, 2018
- 17
Replicated, Seems like a bug in Adguard Desktop.
Changed DNS to NextDNS (With Parental Control) in my Adguard home. All DNS Queries are Sent to NextDNS. (verified using dnstools.check and nextdns homepage )
Visited Adult Site, and it opened successfully, even though it is displayed as "Blocked" in NextDNS logs.
Results are inconsistent, some sites display NextDNS blocked page, some sites open (NextDNS Logs displays them as blocked)
Update: Tested both Edge and Firefox in Incognito Mode. Issues seems to be related to chromium based browsers.
All Adult Sites display NextDNS Block Page in Firefox
Changed DNS to NextDNS (With Parental Control) in my Adguard home. All DNS Queries are Sent to NextDNS. (verified using dnstools.check and nextdns homepage )
Visited Adult Site, and it opened successfully, even though it is displayed as "Blocked" in NextDNS logs.
Results are inconsistent, some sites display NextDNS blocked page, some sites open (NextDNS Logs displays them as blocked)
Update: Tested both Edge and Firefox in Incognito Mode. Issues seems to be related to chromium based browsers.
All Adult Sites display NextDNS Block Page in Firefox
Last edited:
ZeroOne
Level 1
- Mar 8, 2018
- 17
Sure, here are the results:
Edge: This device is using NextDNS with no profile.
Firefox: All good! (profile works).
Palemoon Browser: All Good (Profile works).
- Aug 22, 2013
- 827
Ensure that the following rules in setting>general>advanced setting as exactly like in the given image and then try.
- May 13, 2017
- 2,497
Chromium based browsers try to use DNS by default, even when DOH is strictly set, unless you block it in the firewall. I setup DOH within each browser rather than using DHCP.
Code:
reg add "HKLM\Software\Policies\Microsoft\Edge" /v "BuiltInDnsClientEnabled" /t REG_DWORD /d "1" /f
reg add "HKLM\Software\Policies\Microsoft\Edge" /v "DnsOverHttpsMode" /t REG_SZ /d "secure" /f
reg add "HKLM\Software\Policies\Microsoft\Edge" /v "DnsOverHttpsTemplates" /t REG_SZ /d "https://family.adguard-dns.com/dns-query?" /f
Last edited:
ZeroOne
Level 1
- Mar 8, 2018
- 17
These are Adguard Home (Self Hosted DNS Server) settings. We were testing NextDNS on Adguard Desktop (Desktop Application by Adguard).
- Aug 22, 2013
- 827
No. These are adguard desktop settings. I have taken the image from my desktop pc. Go to settings>general>advanced and scroll down .you will get to see those settings.
- Aug 22, 2013
- 827
That's strange. Do you have any other network drivers installed...like vpn or VMware etc?
- May 3, 2015
- 1,540
This problem with Adguard's DNS settings has been bugging me for years... Thanks!
I didn't connect to the VPN and also exited AdGuard Desktop completely and disabled the security software for testing NextDNS. Also, I noticed the same issue, NextDNS DoH IPv4 not working, on other systems with Microsoft Defender and Firewall only, as mentioned in the other thread.
- Aug 22, 2013
- 827
I don't use native windows doh service. It leaks many dns queries. I use my mikrotik router based doh.
Is the NextDNS app for Windows reliable? What do you suggest between the NextDNS app and YogaDNS, and why?
- Aug 22, 2013
- 827
The nextdns app is okay if you just need Nextdns doh to work. But I suggest yogadns. It has so many customisation options and has zero dns leak. It natively supports Nextdns. If you are interested it can run as a windows system service, which makes it run even before you login. So no chance of dns leak at all. On top of that you can add as many doh dns as you wish.
Tried the NextDNS app, and the outcome was the same, i.e., NextDNS DoH IPv4 when added to Windows 11 didn't work.
Browsed the NextDNS forum and checked a few things.
1. NextDNS DoH IPv4, when added to Windows 11, worked with Firefox but not Chrome and Edge.
2. The suggested fix for Chrome was to disable "Async DNS resolver" in Chrome Flags, but it appears Chrome removed it. No such setting in Edge either.
- Aug 22, 2013
- 827
I was interested in NextDNS because of the native DoH service in Windows 11. AdGuard DNS DoH, too, didn't work with Windows 11. I would continue the Kaspersky subscription or use the free version (which includes all core protection features) instead of installing software for the DNS-based service to work. With Kaspersky, I would get superior protection compared to installing software for the DNS-based service: many and more effective categories (including apps), protection with a VPN connected too, default adult keyword blocking, etc.
I may test the following setup: NextDNS in browsers + Google Search and YouTube set to Safe and Restricted in Windows Hosts (as backup protection).
