Tony Gogoi wrote: > the dns problem was solved. all that happened was that 'named' failed on > all dns servers and had to be restarted on each. > > Any pointers on why "named" stopped on all servers ? The log doesn't > mention anything strange... If named terminates normally, it will write log messages like: Jun 30 19:28:51 cerise named[585]: shutting down Jun 30 19:28:51 cerise named[585]: no longer listening on 127.0.0.1#53 Jun 30 19:28:51 cerise named[582]: exiting It will also remove the named.pid file (typically in /var/run or /var/run/named). If named isn't running, but there are no shutdown messages and named.pid still exists, then named terminated abnormally (e.g. due to a segmentation fault, failure to allocate memory, SIGKILL etc). Apart from anything else, you should check whether the OS vendor has issued an updated version. Bugs have been found in previous versions of named which could result in it crashing if it received a malformed packet. Such bugs have security implications; for exposed network daemons, it is essential to keep up-to-date with any fixes. -- Glynn Clements <glynn.clements@xxxxxxxxxx> - : send the line "unsubscribe linux-admin" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
