named died

[Starrynight_1]

Hi all

I would like to understand why a problem happened today.
That is, sundently the named process died and I had to relaunch it.
I cn??t find any log that can help me and this didn??t happened arround here before.
Does anyone had a similar problem before?

Regars

SN

[Helen French]

Hi,

Check these log files for a possible cause:

/var/tmp/named.run
/var/tmp/named.stats
/var/adm/syslog/syslog.log

HTH,
Shiju

[Bill Hassell]

And of course, get the latest DNS and networking patches.

[Mark Greene_1]

Also, check /var/adm/syslog/syslog.log
you can restart named with the -d option to put it into debug mode, and it will log the debug output here:

/var/tmp/named.run

if you have a primary and secondary dns server setup, it may have died due to a zone transfer that failed.

HTH
mark

[Starrynight_1]

I??ve tried all those options before.
Still I don't find thr error; only this in OLDsyslog.log:

Dec 10 05:33:18 pthp07 named[806]: refresh_callback: zone
ptinternacional.pt/IN:
failure for 144.64.192.97#53: timed out
Dec 11 17:18:12 pthp07 named[806]: transfer of 'telecom.pt' from
144.64.192.97#5
3: end of transfer

and it was before the reboot. And the named was sucessefully started on boot.

...any more ideas?

SN

[Ron Kinner]

It has to store its info somewhere could it be running out of space?

Ron

[Mark Greene_1]

if you cannot tell why named died, start it back-up and use nslookup to debug it.

at your command line, do:

nslookup -swdebug

this will start nslookup and print the nsswitch info. Then you can put it into debug mode:

>set debug

then enter your domain name:

>domain.com

and review the output. You can do an "ls" and list your dns database and if there are errors, you should see them.

The other thing I thought of is to review the last few days' of entries in the syslog.log for errors that may not be dns or nslookup directly related, but perhaps something that, as a side affect, would have killed named.

HTH
mark