Ubuntu
network-manager-strongswan package

  1. Bug #1864256
  2. Comment #8

Comment 8 for bug 1864256

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

Description of problem:

When using NetworkManager to connect to a VPN where OpenVPN pushes DNS configuration from the server (via the dhcp-option setting), these servers are correctly added to /etc/resolv.conf. However, since Fedora 33, the default for name resolution is systemd-resolved, which appears to ignore /etc/resolv.conf and the configured name servers are not used.

Version-Release number of selected component (if applicable):

NetworkManager-openvpn-1:1.18.12-1.fc33.1

How reproducible:

Always

Steps to Reproduce:
1. Connect to an OpenVPN network that configures custom name servers via dhcp-option
2. Observe that these name servers are added to /etc/resolv.conf
3. Try to resolve internal names only served by the custom name servers

Actual results:

Name resolution fails as systemd-resolved ignores the configured name servers

Expected results:

The configured name servers are used and internal names resolve successfully

Additional info:

As a workaround, systemd-resolved can be circumvented by adding "dns=default" to the [main] section in /etc/NetworkManager/NetworkManager.conf