This didn't resolve my problem , of an incorrect /etc/resolv.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769016
Title:
nsswitch.conf doesn't specify 'resolve' to support systemd-resolved
If systemd-resolve's stub DNS resolver is used (which I believe is the
case) then "resolve" directive is optional as DNS requests are routed to
this stub resolver (per the "standard" nss-dns directive) which acts
according to systemd-resolve's logic. I just wrote the above in the
following comment
The necessary (for systemd-resolvd to work properly) package libnss-
resolve is still not included with Ubuntu 18.04 nor Ubuntu 18.10
installs. Manually adding the package fixed the name resolution
problems on an otherwise unaltered installation using DHCP from a
gateway.
--
You received this
For some reason, libnss-resolve package was missing on my system. Now,
it works as expected with the nsswitch.conf change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769016
Title:
nsswitch.conf
Same issue with OpenVPN, but my changes to nsswitch.conf seem to be
ignored.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769016
Title:
nsswitch.conf doesn't specify 'resolve' to support
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769016
Title:
I had the same issue, I was also looking at nsswitch.conf but only after
finding this post and adding the 'resolve' to that conf it started
working normally. I had an other, custom vpnc-script and that one also
worked but can't find it now
--
You received this bug notification because you are a
