-
Notifications
You must be signed in to change notification settings - Fork 200
How to debug when DNS66 isn't blocking ads and other common pitfalls
Go to "Hosts
" tap on the "+
", select Action "Deny
" and add "www.example.org
", Confirm, type the refresh button.
Now check whether you can still enter "www.example.org
" in your browser.
Or visit ads-blocker.com/testing and check whether you're seeing ads (if you're sure that your activated ad lists should block them).
Open chrome://flags
in Chrome and disable Async DNS resolver
& Secure DNS lookups
.
Help fixing this issue by providing information on issue 239.
Go to Settings
> Network & Internet
> Advanced
> Private DNS
Set it to Off
. You can also try Automatic
in case it's still not working but usually users had problems when Private DNS
was not set to Off
.
In that case consider searching for a similar issue (even in the closed ones!). Try similar phrases as well.
Consider opening a new issue if you didn't find anything helpful. Don't forget to add a DNS66 log file (in DNS66: touch the three dots and Logcat
)!