Fedora Account System
Red Hat Associate
Red Hat Customer
When NetworkManager controls dnsmasq, 127.0.0.1 is used as DNS server. OpenVPN is then able to both use the local and remote DNS servers. /etc/NetworkManager/NetworkManager.conf [main] dns=dnsmasq This works, but only during the first connection. Reproduce this by having at least one OpenVPN connection configured. Steps to Reproduce: 1. Make sure NetworkManager controls dnsmasq (dns=dnsmasq) 2. Connect to an OpenVPN server 3. resolve DNS for a host on the network host hostname.example.com hostname.example.com has address xxx.xxx.xxx.xxx 4. Disconnect the VPN 5. Connect again to any OpenVPN server 5. resolve DNS for a host on that network Actual results: host hostname.example.com Host hostname.example.com not found: 5(REFUSED) Expected results: hostname.example.com has address xxx.xxx.xxx.xxx (just like the first time)
(In reply to Alvin from comment #0) > When NetworkManager controls dnsmasq, 127.0.0.1 is used as DNS server. > OpenVPN is then able to both use the local and remote DNS servers. > > /etc/NetworkManager/NetworkManager.conf > [main] > dns=dnsmasq > > This works, but only during the first connection. This is a known issue in dnsmasq, already tracked in bug 1373485. In the meanwhile you can use this workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1338731#c23 *** This bug has been marked as a duplicate of bug 1373485 ***