Ubuntu
network-manager-strongswan package

  1. Bug #1864256
  2. Comment #11

Comment 11 for bug 1864256

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

there are various ways how DNS (with or without NetworkManager) can be configured.

Also, it doesn't seem you are using the default configuration of Fedora 33, where systemd-resolved is used. So, to fully understand the problem, you would have to provide how your system is configured.

For example,

with systemd-resolved, commonly /etc/resolv.conf would be symlinked to a file as explained in `man systemd-resolved`. In that case systemd-resolved will mostly ignore /etc/resolv.conf, and /etc/resolv.conf is commonly not used by glibc resolver (which -- depending on your configuration -- uses NSS modules to directly talk to systemd-resolved (`man nsswitch.conf`)). Thus the symlinked /etc/resolv.conf is mostly not used, but see how this works in `man systemd-resolved`.

Anyway. You need to share how exactly your system is configured.

Possibly, just collect a complete level=TRACE log that shows the issue. Read https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/NetworkManager.conf#n28 for hints about logging (and note the comment about private data in log files).