This is a small hotfix for the recent AdGuard for Android release. Mostly squashing bugs related to the new features introduced in v3.2.
Last edited by a moderator:
Yes. System DNS, AdGuard DNS, any other custom DNS ... it doesn't matter. If the DNS Filter is enabled, all DNS lookups fail.Well, if you switch to another DNS server does the problem still exists?
They have never tested these "hotfixes" beyond their own machines as far as I know.Do u people actually test your updates???
It was tested on the nightly channel for a few days.They have never tested these "hotfixes" beyond their own machines as far as I know.
No. Every Firewall setting is in its default state (everything is enabled/allowed by default). Almost every setting in AdGuard is pretty close to default, if anything I have chosen to disable AdGuard protection (bypass) entirely for many apps.Just in case, could it be that you have network access disabled for all apps by default?
This is not related to AdGuard's firewall functionality. Switching the entire Firewall feature to "Off" and the DNS Filter to "On" still leaves all DNS requests broken.When AdGuard blocks network access for an app, it shows a notification about this and lets you temporarily allow network access for this app.
Well, at least we now know that wasn't it, still broken.Also, please try this build - it has the same changes as .140, but with the previous dnsproxy version:
You have no idea how uncomfortable it is to give out that massive amount of private information each time something in AdGuard breaks.@Purple Tentacle well, I really need to see your logs then.