Ubuntu
network-manager-strongswan package

  1. Bug #1864256
  2. Comment #15

Comment 15 for bug 1864256

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

(In reply to Benedikt Gollatz from comment #4)
> 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.

OK, in this mode, systemd-resolved should indeed be in consumer mode. It should try each server listed in /etc/resolv.conf one at a time. If the first-listed server says the name doesn't exist, then it stops and will not check with the next server.

Have you both *intentionally* configured that setup? I highly recommend deleting /etc/resolv.conf and symlinking it to ../run/systemd/resolve/stub-resolv.conf. This is Fedora's default configuration, and is *much* better supported. I haven't invested any effort into testing non-default configurations.

I understand that some users who have upgraded from much older Fedora releases might wind up with /etc/resolv.conf -> /var/run/NetworkManager/resolv.conf with no user interaction. If so, that's a Fedora bug, and we should probably one-time clobber that configuration in an upgrade scriptlet to ensure everyone who hasn't intentionally manually configured /etc/resolv.conf should get /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf.

> 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.

Hmmm, that is weird. Can you please post the output of 'resolvectl domain' and 'resolvectl dns'? My suspicion is you don't have DNS domains configured properly. NetworkManager should handle that for you so you don't have to think about it, but I guess somehow it's not happening....