-
Notifications
You must be signed in to change notification settings - Fork 116
Closed
Description
Version
AdGuard for Android 4.0
Environment
Any compatible android version
Steps to reproduce
- Launch AdGuard
- Enable protection along with the DNS Protection module
- Go to the Settings tab -> General -> Advanced -> Low-level
- Set the Fallback upstreams to Automatic DNS
- Disable the
Validate DNS upstreamsoption - Open the Protection tab -> DNS Protection -> DNS server
- Add and select the invalid custom dns
1.2.3.4 - Surf some sites
- Open the Statistics tab -> Recent activity
Expected behaviour
Queries are resolved by the fallback upstream.
Actual behaviour
Requests in the recent activity log marked as SERVFAIL. The invalid 1.2.3.4 DNS is still in use.
Additional info
This issue persists for the invalid plain dns, but the invalid encrypted dns upstream switches to the fallbacks correctly.
Reactions are currently unavailable