Major VPN providers offer a GUI application which handles all aspects of the connection.
Every now and then the topics on troubleshooting a given VPN provider surfaces and a lot of topics boils down to DNS and for good reason.
Whether you are using an app offered by your provider or you are using configuration files it is of utmost importance you ensure correct configuration of DNS.
Manjaro default resolver
Since the dawn of Manjaro, the network has been configured using NetworkManager and resolved provided by openresolv package.
VPN provider expectations
All VPN providers maintains compatibility with Ubuntu, Debian and Fedora and as they all use systemd-resolved as DNS resolver, in fact they expect it to be so.
This makes it a - at times, hairpulling - challenge to get the VPN into an functional state where DNS work both before and after connection.
Provider provisioned apps
There is a helper package systemd-resolvconf which provides a symlink to resolvctl in case you are used to resolvconf on the commandline or an older application expects resolvconf to be a working binary.
It should also happen before starting the service.
This should also happen before the service.
It is not required to use systemd-resolved but its main use is to provide backwards compatibility with resolvconf/openresolv … this may be pertinent for various VPNs and other considerations.
(provides symlink for /usr/bin/resolvconf)
Is sudo necessary here? Shouldnt polkit be allowed to handle the permission?
Its been a minute since I did a replacement so I dont recall if restarting NetworkManager or similar would be required. Of course a system reboot would be sure.
Some other info (like using FallbackDNS) are illustrated in some other posts but this bigger one comes to mind;
Oh, and I also am reminded that openvpn-update-systemd-resolved AUR package is handy for anyone using an openvpn connection.
(Pretty much does seamless switching of some tech such as DNS servers before/after VPN connection)
well - one could use pkexec - but for consistency in the sequence … sudo is used
The link is coming after enabling the service because you cannot force a link to a non existing file - and the stub only exist after systemd-resolved has been started.
Yes - various helpers exist - but they are only required if one uses openresolv and the whole intent of the topic is to mogrifiy the end-user’s system to use systemd as resolver.
I think you misunderstand.
The helper script is for openvpn … you know the thing that the majority of VPN providers run on until wireguard became more widely adopted?
Nothing to do with openresolv - the backwards compatibility for that is systemd-resolvconf as covered above.
I have a feeling openvpn-update-systemd-resolved is still useful for many many VPN providers.
Its also related directly to issues such as ‘my DNS servers wont update or change back while or after using VPN.’
Yes - they are are required if one is using OVPN - I have added a section TODO - perhaps you can assist - I haven’t been using ovpn configs for a long time …