NetworkManager not setting given DNS in resolv.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager |
Expired
|
High
|
|||
network-manager (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
-------
# 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:/
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
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:/
- https:/
- https:/
- https:/
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
information type: | Private Security → Public |
information type: | Public → Public Security |
Changed in network-manager: | |
importance: | Unknown → High |
status: | Unknown → Confirmed |
Changed in network-manager: | |
status: | Confirmed → Incomplete |
Changed in network-manager (Ubuntu): | |
status: | New → Confirmed |
Changed in network-manager: | |
status: | Incomplete → Expired |