Open David-Woodward opened 1 year ago
I would expect the container to use the DNS servers pushed to the OpenVPN client by the VPN provider
No, what you would expect, accoding to the docs, is the container using the original container defined DNS server. The docs state it would keep current resolve.conf servers.
However, the problem here is that 1.1.1.1 is still added regardless, that's not the expected behavior according to the docs... @qdm12 So what is wrong here, the docs or the code?
@David-Woodward this is an interesting feature that should be implemented, most likely after #1742 gets merged. We could even add an option such as DNS_OPENVPN_PUSHED=on
to use that.
@Ornias1993
The docs state it would keep current resolve.conf servers. So what is wrong here, the docs or the code?
DNS_KEEP_NAMESERVER=on
does keep your existing nameservers, but it prefixes 1.1.1.1
(or whatever non-localhost DNS_ADDRESS
value) at the top of /etc/resolv.conf
. So both the docs and code should be fine in that aspect. What you want is something different, and I explain the reasoning why 1.1.1.1 is prefixed in this comment, let's continue the conversation there.
Is this urgent?
No
Host OS
Synology Linux
CPU arch
x86_64
VPN service provider
Custom
What are you using to run the container
docker-compose
What is the version of Gluetun
2023-02-27T20:21:31.112Z (commit a97fcda)
What's the problem 🤔
With the environmental variables defined as "DOT=off" and "DNS_KEEP_NAMESERVER=on" I would expect the container to use the DNS servers pushed to the OpenVPN client by the VPN provider. Instead, the cloudflare server 1.1.1.1 is being used.
DNS calls are passed through the VPN provider DNS server as expected when I use a basic OpenVPN-client container configured with the same ovpn configuration file used with the gluetun container. So this would not appear to be a problem with pull/push parameters defined in the configuration file.
Share your logs
Share your configuration