plasma-widget-network-manager override my dns settings

[speedyx]

Binary package hint: plasma-widget-network-manager

On my Kubuntu 9.04 jaunty I can't use the OpenDNS servers as my favourite DNS server.
I modified /etc/dhcp3/dhclient.conf like here:

prepend domain-name-servers 208.67.222.222,208.67.220.220;
#prepend domain-name-servers 127.0.0.1;
request subnet-mask, broadcast-address, time-offset, routers,
        domain-name, domain-name-servers, domain-search, host-name,
        netbios-name-servers, netbios-scope, interface-mtu,
        rfc3442-classless-static-routes, ntp-servers;

I modified /etc/resolv.conf like here:

nameserver 208.67.222.222
nameserver 208.67.220.220

But I still observe I use other dns server in the plasma-widget-network-manager tip that appear when I stay with the mouse over my connection name.

After a connection network-manager override my modified version /etc/resolv.conf with another one:

# Generated by NetworkManager
nameserver 195.128.182.40
nameserver 195.128.182.41

How can I stop this behavior?

I still do what the opendns start page suggest for ubuntu,

              sudo cp /etc/resolv.conf /etc/resolv.conf.auto

but nothing.

[rene (r-launchpad-absorb-it)]

Hi,

i like to run a local DNS and keep it even if I connect to any other network via DHCP. There is an option "DHCP with manual DNS" in network manager settings, but if I enable this I can't connect to the wireless network anymore. DNS was 127.0.0.1, search domains had been left empty. Using DHCP everything works as expected.

Oct 1 12:27:22 sailfish NetworkManager: <info> (wlan0): preparing device.
Oct 1 12:27:22 sailfish NetworkManager: <info> (wlan0): deactivating device (reason: 2).
Oct 1 12:27:22 sailfish kernel: [ 292.423596] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 1 12:27:22 sailfish NetworkManager: <info> (wlan0): device state change: 2 -> 3
Oct 1 12:27:22 sailfish NetworkManager: <info> (wlan0): supplicant interface state: starting -> ready
Oct 1 12:27:45 sailfish NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout): (0) Connection was not provided by any settings service
Oct 1 12:28:06 sailfish last message repeated 2 times
Oct 1 12:28:36 sailfish NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout): (0) Connection was not provided by any settings service
Oct 1 12:29:27 sailfish NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout): (0) Connection was not provided by any settings service
Oct 1 12:30:18 sailfish NetworkManager: <WARN> connection_get_settings_cb(): connection_get_settings_cb: Invalid connection: 'NMSettingIP4Config' / 'dns' invalid: 3
Oct 1 12:30:24 sailfish NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/4 failed to activate (timeout): (0) Connection was not provided by any settings service
Oct 1 12:30:41 sailfish NetworkManager: <WARN> wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/4 failed to activate (timeout): (0) Connection was not provided by any settings service

Regards, Rene

[Jonathan Thomas (echidnaman)]

This is, as far as I know, intended network-manager behavior.

[J Queiroz (zekkerj)]

Try installing "resolvconf" package to force a fixed DNS configuration.