resolv.conf not being written correctly

[hankcurt]

Hi octowaters,

I thought I would let you know how to add entries to /etc/resolv.conf manually and have them stay.

At /etc/resolvconf/resolv.conf.d/ there are three text files named head, base, and tail.  These three files contain the static portions of the /etc/resolv.conf file.  When the network scripts put the file together, they first copy the contents of "head" to /etc/resolv.conf, then add the nameservers configured for your network interface in /etc/sysconfig/network-scripts and finish with the contents of "tail".   I played with it some, and it appears that the contents of the "base" text file aren't used if you have dns servers specified in the interface configuration.

If you look at /etc/resolvconf/resolv.conf.d/head, you will see the warning message that is copied over to /etc/resolv.conf telling you not to edit the file directly.  If under that warning you add nameserver 127.0.0.1, then that entry will appear at the top of your /etc/resolv.conf the next time you restart networking.  Your other nameservers should be automatically added after it.

Hope this helps.

[octowaters]

More likely something wrong with your bind set up, then the resolv.conf setup.

As I found out very very late last night, I have to agree - FULLY - with your idea which is not an idea but a fact.

The boot process screen, in the PCLOS section cries out that *named* FAILS. As you are aware of * named* is part of the Bind package. So there lies the problem

Bind - for a workstation caching server and simple DNS lookup - requires, apparently four files, which are:
named.conf (it is on the system in /etc/)
db.127.0.0. (which does not appear in /var/named/)
ds.cache (which does not appear in /var/named/)
named script file (/etc/rc.d/init.d/ which seems to be there but can t vouch as to the exactness of its calls).

The peculiar history of all this is that I had it working perfectly on my updated PCLinuxOS 2009.1 updated in full. I then took the decision to try out KDE 4 and did not feel confortable with it via the Synaptic upgrade process. As I could not role back, I got fed up and downloaded the ISO for 2009.2 in order to save the updating process (and here lies the problem) the clean install throws up this BIND PROBLEM, and I say, PROBLEM. It's really annoying.

So the issue is NAMED in the KERNEL PROCESS, it just FAILS.

OK. Did I get this over clearly?

[octowaters]

Hi octowaters,

I thought I would let you know how to add entries to /etc/resolv.conf manually and have them stay.

Hope this helps.

Ah, the answer comes out of the well of PCLinuxOS users to fix the "stay there, please"  problem. 

Many many thanks. I don't have to open the bloody /etc/resolv.conf file after a boot to get a net connection every time.

Wish them well there.

Again thanks. An interesting trick, by the way.

Cheers!


Now, the "powers that be" have a chore in fixing the *named* problem in the boot process.

[octowaters]

Been doing some research...

Some questions arise (and some ideas given where stated):
#1. Doing a rpm -qa | grep bind brings up
Bind-devel-9.6.0-1pclos2007
bind-doc....
bind-9.6.0-1pclos2007
bind-utils

#2. To make certain that caching-nameserver is not installed, ran:
rpm -qa caching nameserver
 No result returned, so it is NOT on the system.

#3. Synaptic states that "Note that the
configuration files for making BIND act as a simple caching nameserver
are included in the caching-nameserver package BUT there is NO NAME-SERVER
PACKAGE included. Very helpful, thank you.

#4. It would seem that the required packages (rpm build, Red Hat based) are:
bind
bind-chroot
bind-utils
bind-lib
caching-nameserver

#5. It seems that Mandriva has a problem with this type of install, as reported from
net searches. The two that seem to work are Fedora and Red Hat (well this last understandable
inasmuch as Fedora is basically Red Hat!).

#6. It would appear that caching-nameserver package will have to come from From Fedora, because the Bind site does not have a separate package. Just a crazy idea. 

[MorGotHMGH]

In Pclos 2010 just turn off resolvconf service on start and /etc/resolv.conf is correct after boot.

[wedgetail]

octowaters
I am quite curious, was this an option what MorGotHMGH is suggesting

MorGotHMGH
Better late than never, I was searching the Forum and happened to land in this thread and notice your post count. Welcome to Forum if you have looked around you no doubt have noticed the variety of topics and high degree of activity. May you enjoy the wealth of information and help that can be had.