Hi,
On 03/06/20 19:46, Andrea wrote:
On 03/06/2020 09:04, Jan Just Keijser wrote:
On 03/06/20 09:55, Andrea wrote:
On 02/06/2020 11:59, Jan Just Keijser wrote:
most likely you are using openvpn-systemd-resolved for this - if
so, check the script
/etc/openvpn/update-systemd-resolved
to see how it works. The OpenVPN binary itself does not do anything
with the received DNS settings - it just passes them along to a
plugin or script.
this is a step in the right direction, but it is still not enough
With NetworkManager I get these DNS from resolvctl
Link 6 (tun0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 10.82.0.1
DNS Servers: 10.82.0.1
DNS Domain: ~.
Using the script above I only get
Link 7 (tun0)
Current Scopes: DNS
DefaultRoute setting: yes
LLMNR setting: yes
MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
DNSSEC supported: no
Current DNS Server: 10.81.0.1
DNS Servers: 10.81.0.1
Note the lack of "DNS Domain"
which seems a well known cause if issues.
https://github.com/systemd/systemd/issues/6076#issuecomment-331118330
then I'd say this is an Ubuntu/systemd specific issue, as on my CentOS
and Fedora boxes I do not see this particular issue. After connecting to
the VPN I have the right domain set and the right DNS servers.
Note that there's also a contributed script in the OpenVPN distro
/usr/share/doc/openvpn-2.4.9/contrib/pull-resolv-conf/client.up
which might do what you want.
cheers,
JJK
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
