You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A user that's willing to connect to a hotspot needs to disable DNS filtering (especially DNS servers) first before getting in. It makes using Adguard outside of home kind of cumbersome due to need to switch between many hotspots - you constantly have to turn AG off and then again on, to take advantage of DNS adblocking.
Expected Behavior
Adguard should somehow manage to make hotspots workable while DNS filtering is ON.
Actual Behavior
DNS filtering affects hotspots in a way that it's not possible to connect to them due to DNS issue (most of hotspots require their own DNS servers to log in first).
Additional Information
Andrey said that there might be need to fallback to the system resolver properly (smaller timeout before doing the fallback, like 2-3 seconds (instead of 5 seconds) ).
The text was updated successfully, but these errors were encountered:
Issue Details
A user that's willing to connect to a hotspot needs to disable DNS filtering (especially DNS servers) first before getting in. It makes using Adguard outside of home kind of cumbersome due to need to switch between many hotspots - you constantly have to turn AG off and then again on, to take advantage of DNS adblocking.
Expected Behavior
Adguard should somehow manage to make hotspots workable while DNS filtering is ON.
Actual Behavior
DNS filtering affects hotspots in a way that it's not possible to connect to them due to DNS issue (most of hotspots require their own DNS servers to log in first).
Additional Information
Andrey said that there might be need to fallback to the system resolver properly (smaller timeout before doing the fallback, like 2-3 seconds (instead of 5 seconds) ).
The text was updated successfully, but these errors were encountered: