Replies: 2 comments
-
BTW, I'm using the latest ADH version available from Docker Hub, I've enabled AdGuard log verbosity and it shows
It seems like the problem is with ADH itself. This problem seems very similar to #4655, but mine is version 107 and the test fails immediately. |
Beta Was this translation helpful? Give feedback.
-
Upon closer inspection, I traced the packets back to my main firewall IPTables. |
Beta Was this translation helpful? Give feedback.
-
While testing an ADH instance in a docker container, I can't use TLS upstream domains.
When I try to use a TLS server, ADH fails to test the upstream DNS or respond to any client request.
Test upstream DNS Servers
Using default bootstrap DNS servers:
When I test the DNS server, ADH displays the following error.
When I try an HTTPS server, the connection is successful (
https://94.140.14.140/dns-query
).From the container shell, Netstat shows that the DNS port is open.
What bugs me more is that I have two other setups with ADH and TLS servers and the tests are all successful.
So, I'm lost. Why is it that only TLS is not working in a docker instance?
Beta Was this translation helpful? Give feedback.
All reactions