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

Allow specifying tcp-only and udp-only DNS upstreams #208

Closed
ameshkov opened this issue Nov 1, 2023 · 3 comments
Closed

Allow specifying tcp-only and udp-only DNS upstreams #208

ameshkov opened this issue Nov 1, 2023 · 3 comments

Comments

@ameshkov
Copy link
Member

ameshkov commented Nov 1, 2023

For instance tcp://8.8.8.8 or udp://8.8.8.8

@ameshkov ameshkov changed the title Allow specifying tcp-only DNS upstreams Allow specifying tcp-only and udp-only DNS upstreams Nov 1, 2023
@DandelionSprout
Copy link
Member

DandelionSprout commented Nov 1, 2023

From how I understand it, simply 8.8.8.8 would already be UDP-only, unless there's some backend stuff I'm unaware of.

tcp:// seems to work in AdGuard for Windows. It works in AdGuard Home. And it worked in AdGuard for Android 3.x, making this situation a feature regression.

The original report being closed with the reasoning of "Just use UDP lol" made me stunned, baffled, and speechless.

@ameshkov
Copy link
Member Author

ameshkov commented Nov 1, 2023

simply 8.8.8.8 would already be UDP-only

Not really, 8.8.8.8 is both UDP and TCP, i.e. when the response is truncated it switches to TCP.

@ameshkov
Copy link
Member Author

ameshkov commented Nov 1, 2023

Relevant task: #209

We need to change all products (AG for Win/macOS/iOS/Android) so that they rely on DnsLibs for this functionality.

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

3 participants