-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Listening to TCP [53] is not working #6921
Comments
I'm having similar problems since v0.107.48. |
@zzecool @sweetpants if you use the previous version, does it still happen? |
Have not tried that yet. I'm running in docker, have to get my hands on older images |
Going back to 0.107.25 solved the issue for me. |
Thanks for confirming. Could you please detail exactly how to reproduce the issue? |
I've just updatated the AdGuard, then clicked on disable for 1 hour, and after 1 hour I couldn't navigate anymore |
Hi @notjulian, unfortunately that's not enough information for me to reproduce the issue. I would need to know how you have AdGuard Home setup, and where the issue is happening so I can try reproduce the issue. |
Just install v0.107.48 and try to make a TCP DNS request. |
yes I'm using the latest version, thanks |
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux, AMD64 (aka x86_64)
Installation
Docker
Setup
On one machine
AdGuard Home version
Version: v0.107.48
Action
In my network im intercepting all the TCP and UDP requests and reidirect them to the Adguard DNS.
This works fine for the UDP but fails on the TCP.
Some applications have hardcoded DNS and when those requests done in TCP Adguard failed to proccess them and application hangs or cant provide data.
For example
An application running in android is making a hardcoded DNS TCP Request to google 8.8.8.8:53
Im redirecting the requests to adguardhome DNS server like i do for UDP
Yet the server doesnt respond back.
This has been happened in previous version as mentioned at: [ Listening to TCP is mandatory in some cases ] #521
Expected result
Adguard should respond to TCP DNS Requests
Actual result
No DNS replies
Additional information and/or screenshots
No response
The text was updated successfully, but these errors were encountered: