[Hardy] DNS server (settings in knetworkmanager) are not persistent/they get lost after reboot

[scheuri]

I upgraded from 7.04 to 7.10 to 8.04.
I used the latest updates (as of today 2008-04-19 11:50 am).

I had no problems with 7.04 or 7.10, however, had the similar troubles back with dapper (6.06).

After upgrading to 8.04 and rebooting I had no connection to the internet. the reason for that were the missing entry of the DNS of my provider. So IP-addresses were fine to ping and to connect, but the URLs were not resolved. I added the DNS server in KNetworkManager (KDE 3.5.9), applied the settings and everything was fine.
However, after the reboot those settings about the DNS were lost and I had to re-enter them. That now happens after every reboot.

I am using static IP-addresses (entered with KNetworkManager) which are kept in configuration. DHCP is no option for this machine, I need to enter those DNS manually.

Thanks for looking into this

[Eythan (maurel-fabien)]

Same thing for me, I am using static Ip adresses, but i'm not using KDE. Everytime i reboot, i loose the DNS server and i had to enter them again, using the Gnome panel (i don't know the name).

My resolv.conf after a reboot :

# 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

And after modification :

# 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
nameserver 80.10.246.1
nameserver 80.10.246.129

I'm using hardy 08.04 x86_64 upgraded from gutsy. My system is fully updated (2008-04-21).

[Yuriy Kozlov (yuriy-kozlov)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 91890, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.