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.
Since the dawn of Manjaro, the network has been configured using NetworkManager and resolved provided by openresolv package.
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.
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.
However, if the DHCP and VPN clients use the resolvconf program to set name servers and search domains (see openresolv#Users for a list of software that use resolvconf), the additional package systemd-resolvconf is needed to provide the
/usr/bin/resolvconfsymlink. -- https://wiki.archlinux.org/title/Systemd-resolved#Automatically
The process is simple
Copy and paste these commands and you are done
sudo cp /etc/resolv.conf /etc/resolv.conf.bak
sudo systemctl enable --now systemd-resolved
sudo ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
sudo pacman -Rns openresolv
sudo pacman -Syu systemd-resolvconf
If you want to provide custom DNS entries you can do so in /etc/systemd/resolved.conf
TODO