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 753664 - NetworkManager not setting given DNS in resolv.conf
NetworkManager not setting given DNS in resolv.conf
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: IP and DNS config
0.9.x
Other Linux
: Normal major
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-08-15 18:24 UTC by d3bugg3r
Modified: 2017-07-19 07:42 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot showing DNS settings misleading the user. (63.92 KB, image/png)
2015-08-15 18:24 UTC, d3bugg3r
Details

Description d3bugg3r 2015-08-15 18:24:46 UTC
Created attachment 309334 [details]
Screenshot showing DNS settings misleading the user.

*** THIS IS A COPY/PASTE OF MY PREVIOUS BUG REPOT ON LAUNCHPAD ***
*** SEE https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1482887 ***

-------------------- SYSTEM INFOS ----------------
# lsb_release -rd
Description: Linux Mint 17 Qiana
Release: 17

# dpkg --list cinnamon resolvconf network-manager
ii cinnamon 2.2.16 amd64 Cinnamon desktop
ii network-manager 0.9.8.8-0ubunt amd64 network management framework (daemon and userspace tools)
ii resolvconf 1.69ubuntu1.1 all name server information handler

--------------------------------------------------

So, it looks like a duplicate of https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/382161 but this was on KDE in 2009 and I doubt it would have anything to do with it...

Anyway, here is how to reproduce the problem:
- Go to network-manager settings GUI (network indicator -> Network connections)
- Edit current connection (wlan0 in my case)
- Go to IPv4 settings
- Select DHCP (addresses only)
- Set a DNS server, say 37.59.72.228 (it's the first server from OpenNIC project)
- Click save
- Click disconnect
- Click connect

In the summary, you can see the DNS server you just typed. But if you
# cat /etc/resolv.conf
then you see the DNS server provided by your DHCP server (in my case 192.168.1.1)

So the only way to bypass DHCP's DNS settings is to hard-code the DNS in /etc/resolvconf/resolv.conf.d/head

Since this can lead users to believe that they are using their favorite DNS server while they get answers from their ISP/Hotspot DNS, I checked the 'Security' box.

This could also be related to
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1072899
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/254488
- https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1304437
Comment 1 Beniamino Galvani 2015-08-21 15:11:13 UTC
I'm unable to reproduce this, please attach your /etc/NetworkManager/NetworkManager.conf and NetworkManager log.
Comment 2 d3bugg3r 2015-08-28 13:07:25 UTC
(In reply to Beniamino Galvani from comment #1)
> I'm unable to reproduce this, please attach your
> /etc/NetworkManager/NetworkManager.conf and NetworkManager log.

Hi, sorry I couldn't come back sooner here...

I don't have any log from Network-Manager (I did 'grep -ir network-manager /var/log' and nothing showed up).

Anyway, here is my config:

--- /etc/NetworkManager/NetworkManager.conf ---
plugins=ifupdown,keyfile,ofono
dns=dnsmasq

no-auto-default=xx:xx:xx:xx:xx:xx,

[ifupdown]
managed=false
----------------------------------------------

Did you try on Linux Mint 17 Qiana/Cinnamon 64bit ?
Comment 3 Beniamino Galvani 2017-07-19 07:42:08 UTC
This was reported against an old version of NetworkManager.

I'm closing the bug for now, please reopen if the issue still happens on recent versions, thanks.