Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hotspots and DNS filtering issue (timeout needs to be shorten) #3187

Closed
sevospl opened this issue Nov 4, 2019 · 0 comments
Closed

Hotspots and DNS filtering issue (timeout needs to be shorten) #3187

sevospl opened this issue Nov 4, 2019 · 0 comments

Comments

@sevospl
Copy link

sevospl commented Nov 4, 2019

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) ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants