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

Listening to TCP [53] is not working #6921

Open
4 tasks done
zzecool opened this issue Apr 16, 2024 · 9 comments
Open
4 tasks done

Listening to TCP [53] is not working #6921

zzecool opened this issue Apr 16, 2024 · 9 comments
Labels
waiting for data Waiting for users to provide more data.

Comments

@zzecool
Copy link

zzecool commented Apr 16, 2024

Prerequisites

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

image

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

image

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

@sweetpants
Copy link

I'm having similar problems since v0.107.48.

@ghost
Copy link

ghost commented Apr 20, 2024

@zzecool @sweetpants if you use the previous version, does it still happen?

@ghost ghost added the waiting for data Waiting for users to provide more data. label Apr 20, 2024
@sweetpants
Copy link

Have not tried that yet. I'm running in docker, have to get my hands on older images

@ohadbenita
Copy link

@zzecool @sweetpants if you use the previous version, does it still happen?

Going back to 0.107.25 solved the issue for me.

@ghost
Copy link

ghost commented Apr 21, 2024

Thanks for confirming.

Could you please detail exactly how to reproduce the issue?

@notjulian
Copy link

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
tried to restart the service, and the machine but it didn't solved ...

@ghost
Copy link

ghost commented Apr 22, 2024

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.

@zzecool
Copy link
Author

zzecool commented May 7, 2024

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.

@notjulian
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
waiting for data Waiting for users to provide more data.
Projects
None yet
Development

No branches or pull requests

4 participants