Ubuntu 10.04.4 LTS Server resolvconf — does not work resolving after a reboot?

Hello!


Updated here one server to this new version of Ubuntu and got these new rakes: standard resolv.conf has been replaced by the program resolvconf, and stopped working resowing domain name after you restart the system.


Now, to prescribe the NA server, need to configure them through /etc/network/interfaces

for example:
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, according to the startup order in /etc/rc?.d, /etc/init.d/networking fulfills earlier than /etc/init.d/resolvconf.

Apparently, therefore, after the system startup file /etc/resolv.conf pristine, and restart /etc/init.d/networking restart yields the desired result (in the file the desired record).


The problem can be solved by adding to /etc/rc.local lines like

sleep 30 && /etc/init.d/networking restart


But somehow that's not cool.


Question: why they did so?

Or I something do not understand?


Google does not like me today.
October 8th 19 at 02:45
3 answers
October 8th 19 at 02:47
resolvconf writes the configuration to /etc/resolvconf/run/resolv.conf. Check whether /etc/resolv.conf a link to /etc/resolvconf/run/resolv.conf.
That is, I checked the manual and read it. :) Just /etc/resolvconf/run/resolv.conf is reset to zero when restarting the system. Is created dynamically by commands like "dns-nameservers 192.168.2.2 192.168.2.1" in the network scripts. - Emmy33 commented on October 8th 19 at 02:50
October 8th 19 at 02:49
> But, judging by the start order in /etc/rc?.d, /etc/init.d/networking fulfills earlier than /etc/init.d/resolvconf.
In General, logical. If you are getting addresses by DHCP, then how will you define the DNS servers to raise the network interface?
But how can that be?
In this form DNS'you just are not indicated after turning on the computer until restarting interfaces. - Emmy33 commented on October 8th 19 at 02:52
Question on filling: What is the probability of finishing work resolvconf to networking, if networking is started before? The start order is one thing, but the order of completion of work is somewhat different. - Emmy33 commented on October 8th 19 at 02:55
Hmm... this is what I found:
just run /etc/init.d/resolvconf start killing entry in /etc/resolv.conf - Donald.Rolfson commented on October 8th 19 at 02:58
That actually also makes sense. If resolvconf will not erase old records no auto-detect DNS servers will not. It is strange that after the interface is raised, the DNS apparently yet to be determined. Resolvconf is not the case and forgets to wait until networking is completed? - Emmy33 commented on October 8th 19 at 03:01
Here the campaign is as follows:
— start /etc/init.d/networking and creates entries in /etc/resolv.conf
— start /etc/init.d/resolvconf and kills records

Maybe just remove resolvconf from runlevels? - Juana_OConne commented on October 8th 19 at 03:04
Wait a second... Really, why do you have resolvconf? You've got a static konfiguraciju in /etc/network/interfaces and it seems resolvconf has no otnosheniya. Throw resolvconf from runlevels (maybe even apt-get remove?) and you probably will be happy. - Emmy33 commented on October 8th 19 at 03:07
By the way, found such a bug
bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/558384

The decision — as I described in the beginning. But I'm not sure this is a bug or a feature.

And if to consider that in Ubuntu 12.10 (or 04, can't remember exactly), that resolvconf will work by default, it is strange that there is no normal guide on how to configure DNS.

In fact, in 10.04.4 is already in use resolvconf by default, if I'm not mistaken. - Juana_OConne commented on October 8th 19 at 03:10
kreativf, something tells me that to remove the package is not a good idea. Like, now some programs will use this thing.
Note that now the dns servers should be set through the variable "dns-nameservers" in the file interfaces.

It seems to me that it's just an init script curve from resolvconf. - Emmy33 commented on October 8th 19 at 03:13
In the bugtracker say that without it everything works except that each time you reboot nameserver's added again. The documentation says that to use a variable dns-nameservers you need the package resolvconf. I don't quite understand why, but apparently will have to believe the documentation. - Emmy33 commented on October 8th 19 at 03:16
Most likely, you will start to get packages that can't live without resolvconf.

I just don't quite understand why this package has included in 10.04.4 like this and not told how to solve the problem. - Juana_OConne commented on October 8th 19 at 03:19
Apparently you are not alone, this problem appears not at all. - Emmy33 commented on October 8th 19 at 03:22
October 8th 19 at 02:51
Looks like a bug... Specify them statically from time to time. No brainer I have not yet invented.
the decision-crutch described in my first post :)
and Your advice will not work — the file /etc/resolv.conf is erased when you restart the resolvconf program. - Emmy33 commented on October 8th 19 at 02:54

Find more questions by tags Linux