-
-
Notifications
You must be signed in to change notification settings - Fork 393
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
Bug: DNS resolution issue after v3.40.0 #2630
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
Here's a diff of the DNS portion: https://www.diffchecker.com/dfS5DYAV/ |
Now regarding resolving public names, what error do you get in your logs? 🤔 There was a long overdued jump from Unbound (its own program) to my own Go DNS forwarding server in v3.40.0 (see release notes: https://github.com/qdm12/gluetun/releases/tag/v3.40.0) in order to implement a bunch of new DNS features, one critical one being, as you've seen, resolving local names smoothly (almost done). |
Oh interesting! And thanks for the quick response! v3.40.0Here's the log:
But here's an even more confusing output:
EDIT: Sometimes I do get resolution failure with
It might be because of the healthcheck disconnecting the VPN though:
v3.39.1For reference, here's the expected behavior:
|
What error do you get logged in gluetun when you fail to resolve something?
Note the healthcheck just detects the connection doesn't work and autoheals the VPN, it isn't really the cause disconnecting the VPN |
Is the only log related to The only
The rest is just warnings. |
I am noticing the same issue. I'm running the same version with ProtonVPN and port forwarding. The VPN becomes unhealthy, gets restarted, and then port forwarding and DNS issues occur. It times out for ~2min before becoming healthy, but the port forwarding never happens and starts coming back as 0 from the control server. Have to manually restart gluetun to resolve port forwarding failure. It reports the same port forwarding service error once after the VPN becomes healthy and then port forwarding doesn't run again after that.
|
@dagleaves I also have the same issue using ProtonVPN. I can't even deploy the container - it's just unhealthy from the start. I had to find a workaround using a different package 😢 |
I also bumped into this after upgrading to v3.40.0. Reverting the container image to |
Can confirm this issue too. Happy to test any fixes in the future. |
Is this urgent?
None
Host OS
Ubuntu Server 24.04
CPU arch
x86_64
VPN service provider
NordVPN
What are you using to run the container
Kubernetes
What is the version of Gluetun
v3.40.0
What's the problem 🤔
DNS resolution is not working anymore. I keep getting
WARN [dns] dialing tls server for request IN AAAA example.org.cluster.local.: context deadline exceeded
.I tried executing
wget google.com
in the container andv3.40.0
consistently fails to resolve DNS.Share your logs (at least 10 lines)
Breaking (v3.40.0):
Sane (v3.39.1):
The text was updated successfully, but these errors were encountered: