Operating System - HP-UX
1849843 Members
2129 Online
104044 Solutions
New Discussion

"named" daemon needs to be stop & start after reboot

 
SOLVED
Go to solution
Kong Kian Chay
Regular Advisor

"named" daemon needs to be stop & start after reboot

System : HP-UX 11.0, K570 Server

Our server SERVER99 (a PRI DNS & NIS Server) needs to have its "named" daemon stops & starts again after each reboot (though a "ps -ef" shows that it is running fine). Failure to do so will result in clients having problem --- "ypwhich" returns hex code and "nslookup" error of "Cannot find server name for address: Timed Out".

Note :
- Problem occurs only after installation of QPK1100, Quality Pack for HP-UX 11.0, on 18-Apr-2001.
- any suggestions that require reboot will not receive any immed feedback as our next reboot is scheduled on 2-May-2001.
5 REPLIES 5
Thierry Poels_1
Honored Contributor

Re: "named" daemon needs to be stop & start after reboot

hi,
edit /etc/rc/config.d/namesrvs
and change "NAMED=0" to
NAMED=1


and check if you have following files:
/sbin/rc1.d/K630named
/sbin/init.d/named
/sbin/rc2.d/S370named

good luck,
Thierry.
All unix flavours are exactly the same . . . . . . . . . . for end users anyway.
Pedro Sousa
Honored Contributor
Solution

Re: "named" daemon needs to be stop & start after reboot

Hi!
Did you check for Special installation instructions for each patch you were going to install?
I'm afraid you should do it before, but if you didn't, do it now and check if you find something relating named.

I've checked some patches and I found this insteresting patch:
PHNE_20619 may give some errors with name resolutin
install superseding patch PHNE_23274 (HP recommended - does not require reboot).

good luck.
Kevin Wright
Honored Contributor

Re: "named" daemon needs to be stop & start after reboot

does the reverse DNS work properly after you stop and restart named? Seems like the PTR records are not set up correctly and the gethostbyip is failing on nslookup.
Kong Kian Chay
Regular Advisor

Re: "named" daemon needs to be stop & start after reboot

Would like add the following details :--

1) have verified the problem exists by rebooting the server 3 times on 23-Apr-01, issuing commds "nslookup" & "ypwhich" on clients before stop/start "named" on Server.
2) the "named" daemon was running fine on Server after each reboot. BEFORE stop/start "named" to resolve Clients' problem, issued "ypwhich" & "nslookup" on Server itself. Works fine on Server but NOT on clients.
Kong Kian Chay
Regular Advisor

Re: "named" daemon needs to be stop & start after reboot

Sorry, 1 last point :
3) everything works fine on clients after stop/start "named" on server.