Ubuntu
network-manager-strongswan package

  1. Bug #1864256
  2. Comment #12

Comment 12 for bug 1864256

Revision history for this message
In , benedikt (benedikt-redhat-bugs-1) wrote :

The system I am working with has been upgraded from F32. /etc/resolv.conf is a symlink to /var/run/NetworkManager/resolv.conf. It seems to me that in this case systemd-resolved should be in "consumer" mode and use the nameservers provided there (as stated in the fourth bullet point in the /etc/resolv.conf section of the systemd-resolved man page), but that doesn't seem to happen.

If I use any of the other options listed in that manpage as link targets for /etc/resolv.conf, and connect to the VPN, name resolution for internal names still fails. systemd-resolved doesn't seem to learn about the new servers, so the stub resolver won't resolve those names, and they don't get added to /run/systemd/resolve/resolv.conf either. /var/run/NetworkManager/resolv.conf appears to be the only place where they show up.

My nsswitch.conf provides the following configuration for gethostbyname: files mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] myhostname dns