GNOME Bugzilla – Bug 673793
NetworkManager should be able to *append* VPN DNS servers in resolv.conf instead of prepending them
Last modified: 2013-03-26 14:57:16 UTC
My LAN is governed by an OpenWrt router which runs dnsmasq that resolves the hosts on the LAN by name. Upon connecting to the company VPNC router NetworkManager prepends the VPN DNS servers to my router's address in resolv.conf which breaks local name resolution. I noticed that when I manually change resolv.conf after connecting to the VPN so that my router's IP address gets featured first and the VPN DNS IP addresses are featured last everything works fine. An option should be provided by NetworkManager so that VPN DNS IP addresses could be appended to the LAN router IP, instead of prepending them. (As a workaround I can manually specify the desired DNS IPs in any order I want but this is suboptimal, especially considering that I have to create VPN connections this way for every LAN that I usually use (because of the different router IPs of different LANs)).
I can confirm this bug. I just found the same problem and the same workaround. I made a report with details to the KDE network-management team which can be found here: https://bugs.kde.org/show_bug.cgi?id=298249 They were kind enough to point me towards the upstream bug report.
I just realized one difference, I am accessing an OpenVPN server. All of the details and package versions can be found in the KDE bug report I linked to. Thank you.
Created attachment 212152 [details] Copy of KDE network-management bug report.
There are lots of people who want to slightly tweak resolv.conf management in slightly different ways. Rather than add options for every possibility, we're just going to make it possible to write your own script to write out resolv.conf the way you want it. *** This bug has been marked as a duplicate of bug 656260 ***