Just experiencing some crazy problems with ‘named’ (dns).
Our web server (which is also our gateway to the Internet for our office machines) serves as a DNS and sporadically over the last couple of days, for no known reason, named keeps failing and every now and then (between 15 minutes to a few hours) it will just, stop. I restart it using ‘service named restart’ and it says that the shutdown of named failed, but startup is OK.
Originally (not knowing what the problem was) I reset our web server, so it’s not just some bug in startup, and we have made NO changes that should effect it’s workings at all.
Just weird. =/
I’ve looked through the cronjobs & there’s nothing that even comes close to the failure times, so I can’t see what the problem might be.
Has anyone experienced this sort of thing before, or have any idea what it might be?
Be useful to see some logs from the server. /var/log/daemon.log is a good place to start, depending on your syslog config.
Sounds to me like bind (named) is dying. -- Tony Green <[EMAIL PROTECTED]>
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
