DNS servers not updated in systemd-resolved but it works with the openfortivpn cli
When activating the VPN through the NetworkManager gui, the nameservers are not added to systemd-resolved.
I can't figure out why, as systemd-resolved logs the following messages:
journalctl --unit systemd-resolved.service
Jun 22 13:00:39 seb-desktop systemd-resolved[113816]: ppp0: Bus client set default route setting: yes
Jun 22 13:00:39 seb-desktop systemd-resolved[113816]: ppp0: Bus client set DNS server list to: <dns_server1>, <dns_server2>
(with <dns_server1>, <dns_server2> being the correct ip adresses of the dns servers that should be used with this connection)
However, if I the ask resolvectl for the correct nameserver using resolvectl dns
, the output is:
Global:
Link 2 (eno1): 192.168.178.1
Link 80 (ppp0):
So it didn't actually apply the DNS servers, even though systemd-resolved previously stated that they were set (as stated in the log above).
If i instead use openfortivpn
from the command line with the same username and password as configured in NetworkManager-fortisslvpn, I get a slightly different output:
journalctl --unit systemd-resolved.service
Jun 22 13:15:26 seb-desktop systemd-resolved[113816]: ppp0: Bus client set DNS server list to: <dns_server1>, <dns_server2>
Jun 22 13:15:26 seb-desktop systemd-resolved[113816]: ppp0: Bus client set search domain list to: <domain>
and after that, also resolvectl dns
is outputting:
Global:
Link 2 (eno1): 192.168.178.1
Link 80 (ppp0): <dns_server1> <dns_server2>
I added the output of journalctl --unit systemd-resolved.service
after setting resolvectl log-level debug
and activating the VPN connection through the GUI in this file: dns-debug.txt
Also I noticed, that when I manually set the DNS servers through the gui, resolvectl dns
will still not output a valid dns server for ppp0 but leave it empty instead, as seen above.
Any hint where I could continue to search for the problem would be appreciated.