Internal DNS from Wireguard file not written to resolv.conf

[mielouk]

After updating openresolv in Manjaro testing branch from 3.17.0-1 to 3.17.2-1, my automatic Wireguard VPN connection failed with telling me that DNS couldn't look up entries on localhost. Which is true, because I don't have a local resolver on my machine. I looked at resolv.conf and it was empty.

When disabling the VPN the address of my router got written into resolv.conf and it worked normally.

When trying to force an update of resolv.conf while the VPN was active it showed me this:

sudo resolvconf -u /usr/bin/resolvconf: line 999: fd7d:76ee:e68f:a993::1: command not found

Where the ULA is the internal DNS address of my VPN provider.

After downgrading to 3.17.0 it started working again

Before the downgrade, resolv.conf was empty. Now it shows the internal DNS of my provider:

nameserver 10.128.0.1
nameserver fd7d:76ee:e68f:a993::1

cat /etc/netctl/dhcp

Description='A basic dhcp ethernet connection'
Interface=enp7s0
Connection=ethernet
IP=dhcp
## for IPv6 autoconfiguration
IP6=stateless

If you need further information/logs/journals, please let me know.

[rsmarples]

I'm hoping this is fixed in openresolv-3.17.3.
If not, could you post the output of resolvconf -l please

[mielouk]

Installed 3.17.3 from the Arch repo. Works fine now. Thx!