After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 629258 - Wrong order of nameservers in resolv.conf
Wrong order of nameservers in resolv.conf
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
0.8.x
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Blocks:
 
 
Reported: 2010-09-10 11:53 UTC by Dariush Forouher
Modified: 2011-01-06 08:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Syslog printout (15.64 KB, text/plain)
2010-09-10 11:54 UTC, Dariush Forouher
Details

Description Dariush Forouher 2010-09-10 11:53:58 UTC
System: Debian testing (64bit)
Kernel: 2.6.35

Problem description:
When I simultaneously connect to DUN (via Bluetooth) and to a Wifi network, Network Manager will prioritize the Wifi connection and place the default route through Wifi. Which is just fine. But unfortunately, the nameservers of the DUN are written on top in the resolv.conf, which is bad since they aren't usable outside my GSM provider's network.

Since even the log file says:

"Policy set 'Auto PeopleBot-ITI' (wlan0) as default for IPv4 routing and DNS."

I guess that this is not the desired behaviour.


resolv.conf with Wifi only:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.236.1

resolv.conf with DUN only:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 212.23.97.2
nameserver 212.23.97.3

resolv.conf with both DUN and Wifi:

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 212.23.97.2
nameserver 212.23.97.3
nameserver 192.168.236.1
Comment 1 Dariush Forouher 2010-09-10 11:54:37 UTC
Created attachment 169943 [details]
Syslog printout
Comment 2 Dan Williams 2010-09-17 18:18:40 UTC
So NM always sends the correct resolv.conf information to resolvconf (with wlan DNS on top), but resolvconf is another layer that might re-order nameservers.  Is there a chance you can remove the resolvconf package just for testing to ensure that NM is sending the correct resolv.conf information to the resolvconf program?
Comment 3 Dariush Forouher 2010-09-20 20:41:13 UTC
Yep, you're right. Without resolvconf it works.

Thanks, I'll file a bug over at bugs.debian.org.
Comment 4 T. Hood 2011-01-06 08:51:00 UTC
This patch might solve the problem.

$ svn diff
Index: etc/resolvconf/interface-order
===================================================================
--- etc/resolvconf/interface-order	(revision 154)
+++ etc/resolvconf/interface-order	(working copy)
@@ -10,5 +10,6 @@
 eth*
 ath*
 wlan*
+wifi*
 ppp*
 *
Comment 5 T. Hood 2011-01-06 08:56:47 UTC
(That patch will fix the problem of a wifi* interface not being prioritized before a ppp* interface.)

What is the name of your DUN interface?  And of your Wi-Fi interface?