Ubuntu 10.04.4 LTS Server and resolvconf - resolving not working after reboot?

Question

linux

Hello!
I updated one server here to this new version of Ubuntu and got such a new rake: the standard resolv.conf was replaced with the resolvconf program and rezoning of domain names stopped working after the system was restarted.
Now, in order to register the NS servers, you need to configure them through /etc/network/interfaces
, for example, like this:

auto eth1<br/>
iface eth1 inet static<br/>
 address 223.98.211.123<br/>
 netmask 255.255.255.248<br/>
 <b>dns-nameservers</b> 192.168.2.2 192.168.2.1<br/>
 <b>dns-search</b> company.com<br/>

The idea is good, but...
But, judging by the startup order in /etc/rc?.d, /etc/init.d/networking runs before /etc/init.d/resolvconf.
Apparently, therefore, after the system starts, the /etc/resolv.conf file is pristine, and restarting /etc/init.d/networking restart gives the desired result (the necessary entries appear in the file).
The problem can be solved by adding a line like
sleep 30 && /etc/init.d/networking restart to /etc/rc.local
But somehow this is not cool.
Question: Why did they do this?
Or I do not understand something?
Google doesn't like me today.

Answer 1

resolvconf writes configuration to /etc/resolvconf/run/resolv.conf. Check if /etc/resolv.conf is a link to /etc/resolvconf/run/resolv.conf.

Answer 2

> But judging by the startup order in /etc/rc?.d, /etc/init.d/networking runs before /etc/init.d/resolvconf.
In general, it is logical. If you have to obtain an address via DHCP, then how will the DNS servers be determined before raising the network interface?

Answer 3

Looks like a bug... Write them statically for the time being. I haven't come up with anything smarter yet.