Comment 2 for bug 1768203

I was able to solve my problem by setting the dns-priority of my VPN connection to a negative value: `nmcli connection modify <connection_name> ipv4.dns-priority -100`. You might be able to resolve your issue by setting the dns-priority of your VPN connection to a *higher* value (e.g. equal to that of the other connection). You can view the dns priorities of your connections by running `nmcli connection show <connection_name>` (the default seems to be 0).