AdGuard for Android - 3.2.140 Hotfix

avatar

Administrator
Staff member
Administrator
What was the issue?
Quite the opposite to what I thought it was:)

Filtering was disabled for the "DNS" meta app so AdGuard didn't even try to filter it and bypassed DNS requests to a non-existing DNS server instead of redirecting it to the DNS proxy.
 
So why wasn't that caught during internal testing or nightly flighting? Why was it so hard to reproduce?
Is it not bypassed by default?
Why would it bypass to a non-existing server and not system default, why would it "bypass to" anything? Shouldn't bypass mean "absolutely don't touch at all"? At least that's what the feature description says.
And why wasn't this an issue in 3.2.135 and all previous builds?
 

avatar

Administrator
Staff member
Administrator
So why wasn't that caught during internal testing or nightly flighting? Why was it so hard to reproduce?
Is it not bypassed by default?
Yep, it is not bypassed by default.

Why would it bypass to a non-existing server and not system default, why would it "bypass to" anything? Shouldn't bypass mean "absolutely don't touch at all"? At least that's what the feature description says.
This is due to how DNS filtering works:
1. It configures Android to use a fake DNS address
2. Then when it sees that the connection is to this fake address, the connection is being redirected to the AdGuad's own DNS service

The idea is to not mess with other connections and only filter legitimate DNS requests.

And why wasn't this an issue in 3.2.135 and all previous builds?
DNS was excluded from the regular apps management rules.
 

VC321bx47

New Member
Hmm.... im getting the error after the update if i use firewall for some apps all the dns requests gets blocked
 
Top