NetworkManager doesn't use manual set DNS although there's an option for that

[FriedChicken]

Binary package hint: network-manager

Jaunty, KDE 4.2.4

I liked to use dnsmasq for local dns caching. So I set up NetworkManager using the plasma-widget-network-manager to use 127.0.0.1 as main DNS: In the "IP Address" tab I set "DHCP With Manual DNS" and "127.0.0.1,192.168.2.1" as DNS. I also tried only 127.0.0.1 but it has the same effect.

After dis- and re-enabling the wireless network to enable the new settings (why isn't this done immediately?) resolv.conf always has 192.168.2.1 as DNS. Manual edit of resolv.conf always get overwritten by NetworkManager.

Actually I don't know whether this is a bug in the plasma widget or NM itself.

[Bodra (bodra-swift)]

I have a similar problem. Except If I use "DHCP with Manual DNS", I can't get the wireless to even establish a connection at all. Cchange it back to just plain DHCP and it connects straight away

[bg (bg)]

The same behaviour in Jaunty, KDE 4.3.0 beta 2:

In NetworkManager - Edit Network Connection:
IP Address - Method: DHCP With Manual DNS
DNS Servers: 194.204.159.1,194.204.152.34

cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 194.204.159.1
nameserver 192.168.10.1

[bg (bg)]

Also the behaviour described by Bodra on 2009-06-02 (can't establish the connection when "DHCP with Manual DNS" is used) is present in Jaunty, KDE 4.3.0 beta 2.

[Jonathan Thomas (echidnaman)]

Is this still a problem using the NetworkManager applet shipped with KDE 4.3? It's had many improvements.

[FriedChicken (domlyons)]

I don't know how to test this. KNetworkmanageer seems to replace the plasma widget.

[Bodra (bodra-swift)]

You go to Manage connections -> Wireless tab -> edit connection

Select mode 'shared' and enter a manual dns.

For me it still doesn't work. It just ends up with the dhcp assigned dns.

[Bodra (bodra-swift)]

Although it does actually connect now.

[starslights (starslights)]

hello,

I have same problem on kubuntu karmic alpha 5 64 bits.

I can't choose in network manager my own server DNS like 127.0.0.1.

if i edit resolv.conf, it's automatic rewrite to original. I don't see anymore the possibility to use the eth0 with personnal server DNS.

network manager 0.8

[Jonathan Thomas (echidnaman)]

The (now future) plasma widget and the tray applet (KNetworkManager) both use the same internals for network connections.

[Jonathan Thomas (echidnaman)]

Does this work if you specify a gateway? There was a bug recently fixed in upstream svn where manual connections wouldn't be saved if the gateway wasn't specified. (http://bugs.kde.org/206115)

[Jonathan Thomas (echidnaman)]

Ah, if it fails with DHCP it could also be this bug, also recently fixed: https://bugs.kde.org/206208

[starslights (starslights)]

fixed with recent update for me.

my best

[Jonathan Thomas (echidnaman)]

Then it's likely that in between these two fixes that this issue was fixed. Thanks for the response.

[Rory McCann (rorymcc)]

I have this problem with GNOME NetworkManger.

I right click on the network manager applet -> edit connections -> wireless -> select the wireless connection I'm using now -> click edit -> change to IPv4 Settings -> change the method from "Automatic (DHCP)" to "Automatic (DHCP) addresses only" -> fill in my custom DNS servers in the DNS Servers box -> click apply.

I then look at /etc/resolv.conf and that file hasn't changed. And it's still using the original DNS servers. I know this because my ISP has started DNS hijacking, and they recommend changing DNS servers to 'opt out'

[Rory McCann (rorymcc)]

this still affects network manager

[Rory McCann (rorymcc)]

actually after editing the connection it used the new DNS server on the next start up. However I expected it to be instant apply, like all GNOME applications. There was no indication that I needed to log out / log in to make it work

[Aron Schatz (aronschatz)]

Using Jaunty or Karmic, this bug is not fixed. First, the NM dialog is very unhelpful in setting up static DNS settings. For instance, my wired connection is eth1 and it says "Auto eth1" on the NM applet. The problem is that I can't edit this connection. I make a new connection called "Main" and set it to connect automatically and only use eth1. How do you stop "Auto eth1" from connecting instead of "Main?"

Setting "Main" with DHCP with static DNS does not edit resolv.conf. A reboot didn't help since NM selects "Auto eth1" instead of main. The NM applet needs a better front end, that's probably what a majority of these bugs are coming from.

[Tony Espy (awe)]

Rory, you *should* be able to just Disconnect, and then re-connect the interface in order to pick up the new settings. You shouldn't have to log out. Its not really feasible to apply the settings immediately to a "connected" connection.

[Tony Espy (awe)]

Aron, you've described a couple of issues, which although related, should be considered separate problems with their own bugs.

Please re-test the latest Karmic daily image ( which is essentially the RC for the final Karmic release ), or if you already have a Karmic install, make sure you've pulled down all the updates for it. If you continue to experience the problems described above ( "Can't edit auto eth0", "Can't make Wired connection default", "Static DNS settings don't work" ), then please report them as three separate bugs using the command "ubuntu-bug network-manager" ( via a terminal or Alt+F2 / Run application ).

[Schmirrwurst (schmirrwurst)]

I'm using an updated karmic, and I've also the problem that when I use DNS only for adresses, the DNS information is not applyed by network manager... (kde).

[Frank Meerkötter (frank-meerkoetter)]

I have the same problem with Karmic RC1. The generated /etc/resolv.conf will never contain the manually configured servers.

[Antonio Costantino (anto-costantino)]

I can confirm this with karmic final release on kubuntu: /etc/resolv.conf never changes when DNS are configured manually. I'm changing knetworkmanager in plasma-widget-networkmanagement.

[Antonio Costantino (anto-costantino)]

Sorry, should I re-open the bug?

[Antonio Costantino (anto-costantino)]

I mean, please, can any one tell me if this is a kubuntu or a kde bug? Should I move it upstream?

For those hit by bug 417757 and this one simultaneously, like me, it is impossible to have a decent internet experience by installing pdns-resolver, because pointing dns to 127.0.0.1 will not work! -- and by the way, personally, I can't even use wicd...

[Rory McCann (rorymcc)]

Tony: OK that makes sense and is consistant with my experiences. If logging in then logging out picks up the new DNS, then it makes sense that reconnecting would also apply the change.

However there was no indication that I should reconnect. I was confused and thought that the change would apply. I suggest some static text on the dialog ("Please disconnect then reconnect to apply your changes"), or a popup dialog with the same text when the DNS changes, or a popup dialog saying "In order to apply your new DNS settings, your network must be disconnected then reconnected. Do this now? [Yes] [No] [Cancel]", or something similar.

To have nothing happen (i.e. the way it is now), just leads to user confusion.

[Dhaval Patel (dhuv)]

I just updated to 4.3.4 in Kubuntu and this is still a problem. The manually set DNS servers for a particular network do not take effect.

[Swâmi Petaramesh (swami-petaramesh)]

Confirming this bug on 2 machines with Kubuntu Karmic, all updates applied.

DHCP will define our DSL box as DNS server, although it's dreadfully slow resolving requests. If trying to override that by setting manually the ISP's DNS server in knetworkmanager, the setting is ignored and the connection always defines the router box as DNS server.

That's a pain :-/

[Abhinav Modi (abhinavmodi)]

What further information is required to set this bug to confirmed ? As Swami wrote in #27, this is still seen with latest karmic.

[Artem (artemr)]

Same for me on Karmic with KDE 4.4 RC1

[Jonathan Thomas (echidnaman)]

Not a bug in NetworkManager itself.

[Jonathan Thomas (echidnaman)]

A fixed package has been uploaded to Lucid. I'll look in to getting an update for Karmic going.

[Jonathan Thomas (echidnaman)]

Ugh, the patch won't apply to the version in Karmic proper. The program has changed too much. :(
I won't be able to SRU this fix, but I can update the package in the KDE 4.4 PPA.

[Guenther Palfinger (guenther-palfinger)]

I confirm the bug for KDE 4.6.00 PPA packages under maverick.