Purple Tentacle
Member
Yeah, that may have fixed it. Looking good so far, acting normal with DNS filter en- and disabled. 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.
Purple Tentacle
Member
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?
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?
Yep, it is not bypassed by default.
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.
DNS was excluded from the regular apps management rules.
D
Deleted member 25072
Guest
Hmm.... im getting the error after the update if i use firewall for some apps all the dns requests gets blocked
D
Deleted member 25072
Guest
no if use the NIGHTIY version problem persists it wasnt before
M