[Solved] My system is not routing DNS queries through my VPN (Proton)

bowlin · Yesterday 20:42:09

Hey. Been battling with setting up ProtonVPN (With Wireguard) on my PC, it proved to be more manual work than I expected.

That aside, ipleak.net shows my ISP's DNS, when I'm connected to the VPN. My Wireguard VPN config has this line:

DNS = 10.2.0.1, fd54:20a4:d33b:b10c:0:2:0:1

So it should be routing it through but it isn't.

resolvectl status shows following for the interface:

Current Scopes: none
         Protocols: -DefaultRoute +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
     Default Route: no

I'm using systemd-resolved, as suggested by https://wiki.archlinux.org/title/ProtonVPN

Thanks in advance.

Last edited by bowlin (Today 19:34:05)

-thc · Yesterday 21:31:05

AFAIK the "wg-quick" method to bring up a VPN via wireguard-tools works as a resolvconf/openresolv client.

You need to install the "systemd-resolveconf" package. wg-quick calls this binary and systemd-resolved should add the interface.

Last edited by -thc (Today 10:25:38)

bowlin · Today 14:52:20

Alright. Installed it, removed openresolv because it was conflicting. Now it indeed has the interface in resolvectl, current DNS and all.

Although https://ipleak.net/ still shows my ISP's DNS server for some reason.

-thc · Today 16:53:42

ipleak.net shows my providers DNS server too - even though I'm using a local caching DNS server without forwarding of queries.

bowlin · Today 19:33:16

Oh , well I guess it doesn't matter then anyways. More importantly the interface shows up, thanks for the help.

Last edited by bowlin (Today 19:33:33)

Arch Linux