Name resolution fails for external VPN network using openconnect

buttons · 2017-03-01 02:13:32

Hello all

As the title suggests, I can't resolve any names (fully qualified or otherwise) behind my VPN which I connect to for work through openconnect. The last time this bug happened, it was because Arch had changed /etc/nsswitch.conf to have the following line (in bold):

# Begin /etc/nsswitch.conf
passwd: compat mymachines systemd
group: compat mymachines systemd
shadow: compat
publickey: files
hosts: files mymachines resolve [!UNAVAIL=return] dns myhostname
networks: files
protocols: files
services: files
ethers: files
rpc: files
netgroup: files
# End /etc/nsswitch.conf

and since openconnect doesn't actually work with systemd resolved, I had to move "dns" before "resolve" to get it to work.

Now, after some upgrade (any time in the last three months, haven't been using the VPN that much) it doesn't work anymore. Anyone have any ideas as to where I should start looking?

Last edited by buttons (2017-03-01 02:14:26)

buttons · 2017-03-01 02:20:57

Almost immediately after I posted this, I realized that after connecting /etc/resolv.conf isn't updating correctly upon connection anymore. The domain is correct, but not the nameserver, which seems to be set to localhost no matter what. Manually changing the nameserver to the IP of the DNS behind the VPN works.

What changed to make resolv.conf not update correctly?

Arch Linux

#1 2017-03-01 02:13:32

Name resolution fails for external VPN network using openconnect

#2 2017-03-01 02:20:57

Re: Name resolution fails for external VPN network using openconnect

Board footer