On 2011-07-02, Erwin Mueller <erwin.muel...@deventm.org> wrote: > On Thursday, June 30, 2011 06:00:33 PM Zenaan Harkness wrote: >> Static ip, resolvconf installed, I even went so far as to purge >> uninstall dhcp3-client, and yet: >> on each reboot, resolv.conf comes up empty (no nameservers).
> You are missing the obvious thing: > >> # 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 61.88.88.88 > > You can either edit the file /etc/network/interfaces > > auto eth0 > iface eth0 inet dhcp > dns-nameservers ip.addresse.des.nameservers << add this This is what I had - if you look at my earlier email(s) you will see I had dns-nameservers line in /etc/network/interfaces, which is why this 'problem' is so baffling to me. > Or the file /etc/dhcp3/dhclient.conf Not relevant because I'm not using dhcp. I even removed dhcp3-client and that did not fix the problem. But as per Eric's suggestion, removing the package resolvconf also did the job, since server has no requirement for network settings to be changed once set. BUT, if it were my laptop, not a server, and I wanted resolvconf so I could include dns-nameservers lines in /etc/network/interfaces, then I should still get a proper network config on first boot, _without_ having to run /etc/init.d/networking restart just after first boot. I would have guessed that perhaps there's some interplay between dhcp-client and resolvconf, but the fact is this "no dns servers on initial boot" 'bug' appeared with and without dhcp3-client installed. Zen -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
