gnome-system-tools network-admin does not play nicely with resolvconf

Thanks for your bug. What version of Ubuntu do you use?

On Fri, Sep 15, 2006 at 07:31:27AM -0000, Sebastien Bacher wrote:
> Thanks for your bug. What version of Ubuntu do you use?

Dapper.
If you need additional info, please let me know.

--
Søren O.

"Oh, bother" said the Borg, "we've assimilated Pooh".

You wrote "only the boilerplate info about it being a dynamically generated file", resolv.conf has no such comment on a default installation. Do you use the "resolvconf" package?

Hi,

On Mon, Sep 18, 2006 at 11:54:19AM -0000, Sebastien Bacher wrote:
> You wrote "only the boilerplate info about it being a dynamically
> generated file", resolv.conf has no such comment on a default
> installation. Do you use the "resolvconf" package?

[boll@andariel ~]$ dpkg -l|grep resolvconf [18:23]
ii resolvconf 1.34ubuntu2
nameserver information handler
[boll@andariel ~]$

I obviously don't use it directly, I assume the network-admin gui uses it
behind the scenes.

--
Søren O.

"Oh, bother" said the Borg, "we've assimilated Pooh".

it's rather breaking the config than being used by g-s-t, reassigning the bug to resolvconf, that's an universe package and not part of the stock Ubuntu installation

I can confirm this as an existing problem. In my case, I used DNS Suffixes because of special circumtances. When I use Gnome-Network, it updates the /etc/resolv.conf file. Now, in my case I use DHCP and the DNS Suffixes. So, when Gnome-Network reconnects, it updates /etc/resolv.conf automatically, making my DNS Suffixes disappear. The problem lies in the fact, that Gnome-Network works together with dhcp3, where the configuration is stored in /etc/dhcp3/dhclient.conf.
So the main problem is, that if I want to make the Gnome-Network remember my DNS Suffix settings, I have to manually update /etc/dhcp3/dhclient.conf, and add the following : "prepend domain-name "something.com hu.something.com blog.something.com "; (the space is at the end neccessary, otherwise the DHCP client will give the current DNS Suffix extracted from the DHCP server wrong)
The solution would be, that gnome-network would update /etc/dhcp3/dhclient.conf in case of DHCP, and not resolv.conf. This way changes can be stored for a longer period, and would not go lost after each reconnection.

Does Gnome-Network still break /etc/resolv.conf managed by resolvconf in Jaunty or Lucid? I'm a KDE user, but AFAIK newer GNOME versions use a frontent to network-manager. network-manager is aware of resolvconf and should not produce this problem, anymore.

If the problem still exists, the proper fix would probably be to make Gnome-Network aware of resolvconf.

Possibly the same issue as http://bugs.debian.org/258553 -- gnome-system-tools incompatible with resolvconf

Elaborating...

gnome-system-tools is incompatible with resolvconf and repeated attempts in the past to modify g-s-t to make it resolvconf-compatible led nowhere.

And last time I checked, g-s-t's manner of network configuration was also incompatible with ifupdown if logical interfaces are given names different from physical interfaces. Basically, g-s-t does not play well with Debian network configuration tools.

So either don't use resolvconf or don't use the network configuration feature of g-s-t.
--
Thomas Hood
Debian resolvconf maintainers

Moving back to gnome-system-tools as there isn't much we can do in resolvconf to deal with packages directly poking /etc/resolv.conf.