[network-admin] needs dns-nameservers line in /etc/network/interfaces for static IPs

I can confirm that my manually set DNS server in network settings dissappears
after each reboot. My /etc/network/interfaces is also missing that
dns-nameservers line.

I think the package should be changed to gnome-system-tools. That is the package
containing the network settings dialog.

I have the same problem on 5.10 and 6.06. After reboot my boxes are still on the net, but can't resolve any adresses.
I have to add the DNS manually again to the resolv.conf-file.

However, I do not agree that this is a gnome-system-tools problem only as I am using KDE and CLI, but no Gnome. So I think that this problem is caused "deeper" in the system.

I get my DNS removed and have to add them again in the network thing, but in my case I don't need to reboot, they delete "themselves" every half an hour approximately.

I have dynamic IP and static DNS.

I can confirm this bug on kubuntu 6.06.

Adding a DNS server using the GUI (K->System Settings->Network Settings->Administrator Mode-> Domain Name System-> Add...) is not persistent across reboots.

Manually adding "dns-nameservers xxx.xxx.xxx.xxx" in /etc/network/interfaces resolves the issue.

I guess that new users are not expected to figure this out.

According to "man interfaces" the suggested adding of "dns-nameservers xxx.xxx.xxx.xxx" to /etc/network/interfaces is actually not officially documented.

I cant find any option in "man interfaces" which is "dns-nameservers".

I therefore still confirm (now on a clean Ubuntu 6.06 Final Server Install, using manual network configuration during installation) that Ubuntu does NOT store the DNS servers (whereever that should be) and therefore cant resolve dns-names. However, is able to ping their IP-adresses.

I can confirm this is not a gnome-systems-tools issue, as I encountered it both in KDE and in GNOME. In fact in KDE it was more severe, as the nameservers would reset every few hours, while in GNOME it improved to once every reboot.

To Miranche:

Well, I had GNOME and it happened more often than every few hours. I don't remember if rebooting improved it but I think it wasn't much use.

Is that bug specific to resolvconf use? j^, the bug is assigned to you, are you still working on it?

[quote]I can confirm this is not a gnome-systems-tools issue, as I encountered it both in KDE and in GNOME. In fact in KDE it was more severe, as the nameservers would reset every few hours, while in GNOME it improved to once every reboot.[/quote]

it is a networkmanager issue, it updates resolv.conf

I'm the OP. The status of this bug is "Needs info" -- where do I find out what info is needed?

Or should I close out the case? Since it seems no one is working on it.

Or can I unassign it from j^, so that maybe it will get assigned to someone else that actually moves forward with it?

Just not sure what to do here.

Marking unconfirmed and unassigned. Not clear that's a gnome-system-tools problem, nobody is working on it because there is too many bugs for the number of people working at fixing them at the moment and that one is a corner case (resolvconf is an universe package), the best way to get that fixed would be to debug it and send a patch

I don't remember putting it in gnome-system-tools, maybe someone recategorized it?

Regardless, I'll close this out then since there's no point in having it open if it should come from somewhere further upstream. (I guess I had assumed bugs were passed along upstream for the end-user, the way RedHat seems to do.)

Unfortunately, this isn't one I know how to patch, which is why I opened a case as opposed to fixing it & submitting the change.

Since it seems indeed to be a wider-spread problem not specific to Ubuntu, I'll close this out.

We do send lot of bugs upstream, the question is to know who upstream is for that problem, we prefer to get useful informations first and then forward

Then, once again, I ask: what information is needed, in addition to what was stated in the original problem description?

I (and others, I'm sure) would be happy to provide additional info but need some guidance on what would be useful.

No information is required, the bug is no "Needs Info", what is required is somebody understanding the request (what dns-nameservers), using resolvconf and wanting to forward that upstream. We have thousand of desktop bugs open and very few people working on them, resolvconf is not part of the default installation and not a priority for the desktop team

Hi there
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try the development version Hardy Heron?

Thanks in advance.

Hi Basilio,
I am currently experiencing this exact bug on my Gutsy install. I have to manually re-enter my DNS entries upon each restart. I have not yet tried adding the line to /etc/network/interfaces , but I will. However in the effort to make Linux more user friendly - and thus GUI based, I think that this is something that could be beneficial to improve.

Thanks!

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Martin Mai wrote:

> We were wondering if this is still an issue for you. Can you try with
> the latest Ubuntu release?

Yes, it works in Intrepid.

Erik
--
-----------------------------------------------------------------
Erik de Castro Lopo
-----------------------------------------------------------------
Open Source and Free Software means that you never sacrifice quality
of the code for meeting deadlines set up by people not participating
directly in the software development process.

Thank you Erik. Thus I am closing this bug due to your last comment regarding this being fixed in Intrepid.

Will this annoying and serious bug in an basic system admin tool not be fixed in older versions too ???
And shouldn't the subscribers of this bug be getting informed about a fix in older versions ?

Claudius, it would be good if someone had Ubuntu 8.04 installed to try it with that release, because it's an LTS version and since this bug had the importance "wishlist" it probably does not qualify for even backporting it (except for an LTS version eventually). If you think it qualifies then please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages. Thanks.