DNS server settings don't survive a reboot

Bug #49917 reported by Lorenzo J. Lucchini
2
Affects Status Importance Assigned to Milestone
kdeadmin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: knetworkconf

I'm using Kubuntu Dapper.
I have a static IP. My DNS server is 192.168.0.1.

I go to K menu / System Settings / Network Settings / Administrator mode / (my password) / Domain Name System / Add / 192.168.0.1 / Apply.

After doing this, I can resolve host names. However, by next reboot I cannot anymore, and I have to repeat the entire procedure.

In System Settings / Network Settings / Network Interfaces, eth0 is set to "Manual" (i.e. not DHCP).
If I type "ps aux | grep dh", I don't see anything running, so I don't think a DHCP client is overriding my settings.

Revision history for this message
Luka Renko (lure) wrote :

Please attach the following files to this bug:
/etc/network/interfaces
/etc/resolv.conf

You should do this immediately after the boot (before changing settings manually again)

Changed in kdeadmin:
status: Unconfirmed → Needs Info
Revision history for this message
Lorenzo J. Lucchini (ljl) wrote :

Well, please note that I have now manually modified my /etc/network/interfaces to make the settings "stick" (by adding a "dns-nameservers" entry manually).

However, I will restore the file to the status it was originally after my Kubuntu installation, and the proceed as you suggested.

Revision history for this message
Lorenzo J. Lucchini (ljl) wrote : Files before touching the KDE settings

These are my resolv.conf and interfaces files as they originally looked.
As I mentioned, I have later modified interfaces manually to add a "dns-nameservers" entry, but I'm pretty sure this version I'm uploading has those changes properly reverted.

Revision history for this message
Lorenzo J. Lucchini (ljl) wrote : Files after changing the KDE settings, before reboot

These are my resolv.conf and interfaces files after setting a DNS server in KDE's control panel applet (like described in the bug report), but *before* a system reboot.
(Note that I have not set a domain name here, only a DNS server; however, adding a domain name, too, behaves similarly).

Revision history for this message
Lorenzo J. Lucchini (ljl) wrote : Files after changing the KDE settings, after reboot

These are my resolv.conf and interfaces files as they appear after setting a DNS in KDE's control panel applet, and after the system has been rebooted.

Revision history for this message
Luka Renko (lure) wrote :

Your /etc/resolv.conf has this comment:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN

Do you have resolveconf package installed from universe?
http://packages.ubuntu.com/dapper/net/resolvconf

Can you try removing this package and see if it helps?

Revision history for this message
Lorenzo J. Lucchini (ljl) wrote :

Yes, I had that package installed (I believe it is a standard Kubuntu package), and removing it helped.
Now KDE's settings seems to stick in /etc/resolv.conf.
I suppose that either resolvconf should be removed from the default Kubuntu packages, or the KDE Network settings should be made to modify /etc/network/interfaces rather than /etc/resolv.conf - does that sound right?

Revision history for this message
Luka Renko (lure) wrote :

resolvconf package is for sure not part of standard Kubuntu install as it is in universe repository (and stuff from universe are never installed by default).

The only other package mentioning resolvconf is avahi-dnsconfd, which lists it as Recommends - it is possible that you got this package installed as by aptitude which by default installs Recommended packages.
Did you install avahi-dnsconfd.

I think we can close this bug as Rejected (unless somebody thinks that Recomends has to be changed).

Revision history for this message
Lorenzo J. Lucchini (ljl) wrote :

I suppose you can close the bug, though I have no idea where resolvconf could have come from if it's not a default package (no, I don't have avahi-dnsconfd installed).

Actually, I think it might have come from postfix, which lists it as a Recommended, and which I think was installed by some program I installed right after my Kubuntu was set up (but I later removed that program, whatever it was).

If my recalling of this is correct, though, I don't see why resolvconf has been kept installed: if I used aptitude, it should have removed it when removing the other package, and if I used apt-get get, it shouldn't have installed it at all since it's just a recommend.

Luka Renko (lure)
Changed in kdeadmin:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.