named / DNS

[alieneyes]

Somehow the named service is now starting everytime I reboot my SCO 5.05 server. It seems strange because this systems has been up for 6 months. This behavior must have been caused by some recent event. It appears that it is triggered by a script in the /etc/rc2.d directory. I am not sure which script it is ? Question: When where and how is named started.

I recently added the file /etc/resolv.conf to use my ISP's DNS. It appears that somehow the presense of this file is causeing named to try and start at boot up.

My main concern is it is causing allot of error/entries to appear in the /usr/adm/syslog. It also appears to cause a delay in the login proccess.

Any thoughts,suggestions, or moral support. [sig][/sig]

 

[bigscouse]

On my Solaris system named is started by /etc/rc2.d/S72inetsvc.

I am a bit confused, are you expecting it not to load at boot? [sig]<p>Ged Jones<br><a href=mailto:gedejones@hotmail.com>gedejones@hotmail.com</a><br><a href= > </a><br>Top man[/sig]

 

[alieneyes]

I do not want my server acting as a Primary or secondary DNS athority. I simply want it to act as a DNS client and resolve names through another DNS server.

Instead of configuring DNS I would simply like to use /etc/resolv.conf

My problem is that since I added the file /etc/resolv.conf
DNS (NAMED) is now trying to start when I reboot.

Any ideas. [sig][/sig]

 

[bigscouse]

What are the contents of resolved.conf it should be something like this: -

domain mydomain.com
nameserver 111.11.1.11
nameserver 111.11.0.10
options retry:1

The 1st nameserver entry being the DNS and the 2nd being the backup DNS. [sig]<p>Ged Jones<br><a href=mailto:gedejones@hotmail.com>gedejones@hotmail.com</a><br><a href= > </a><br>Top man[/sig]

 

[alieneyes]

nameserver 123.456.789.0
nameserver 123.456.789.1
domain mydomainname.com


This is what the file looks like.

[sig][/sig]

 

[AndyBo]

I've not got a OpenServer box to hand, but this sounds like a brain-dead startup script starting named just because it can find /etc/resolv.conf.

Go to /etc/init.d (or equivalent) and run &quot;grep resolv.conf *&quot;. This will give you a list of files containing references to resolv.conf. You will need to comment out some code in the script. Look for lines similar to:
[tt]
if [ -f /etc/resolv.conf ]
then
/usr/sbin/in.named
fi
[/tt]
Comment these out, restart your server, and named should stop running. If it is still running, grep for &quot;named&quot; in the init.d files and see what is causing it to start up. [sig]<p> Andy Bold<br><a href=mailto: > </a><br><a href= > </a><br>"I've probably made most of the mistakes already, so hopefully you won't have to..." Me, most days.[/sig]

 

[alieneyes]

# grep resolv.conf *

S85nis: if [ -f /etc/resolv.conf -o -f /etc/named.boot ] ; then

Appearently NIS is the source of my problem.
[sig][/sig]

 

[alieneyes]

Question:

Since I have only one SCO openserver BOX running on my network, everything else is NT. I do not see any real value in having NIS run. Would it make since to remove the S85nic script from the /etc/rc2.d directory. Or would it be better to just remark out the following line:
if [ -f /etc/resolv.conf -o -f /etc/named.boot ] ; then

I guess I am looking for a subjective opion on what would be the better approach.

I am inclined to leave the S85nic script in place and simply remark out the above line and see what happens on the next boot.

Interetsing every script after S85nis did not execute on my last boot.

[sig][/sig]

 

[AndyBo]

Some confusion here about the name of the script... If it's S85nis, then I would just rename it as s85nis. Changing the &quot;S&quot; to lower case stops the script from running at system boot.

If you are not running NIS, then the best thing will be to stop it from running.

If the script is called S85nic, then it might be doing things other than just starting NIS. In this case, you should comment out the &quot;if [ -f /etc/resolv.conf -o ...&quot; line, and any other lines that belong to the same &quot;if&quot; block. (ie, down to the terminating &quot;fi&quot; command.)

If you've already commented out just the &quot;if [ -f /etc/resolv.conf -o ...&quot; line, then this is probably what is causing the other scripts not to execute. You will be getting a syntax error from the S85 script because the remainder of the &quot;if&quot; block has not been commented out.

Hope this helps. [sig]<p> Andy Bold<br><a href=mailto: > </a><br><a href= > </a><br>"I've probably made most of the mistakes already, so hopefully you won't have to..." Me, most days.[/sig]

 

[alieneyes]

typo on my part.

It is the S85nis script.

I am not using NIS so I am going to disable the script by changing it's name to s85nis.

I will post the results once I reboot my SCO box.

Thanks

AndyBo [sig][/sig]