Hello,
This question is more like hitting in the dark, I guess.
We have a primary and secondary DNS server. Twice or thrice so far since "named" automatically failed. Eg. on those times, I simply typed "/etc/rc.d/init/named restart" It showed "STOP - FAILED", "START - OK", after which things were normal.
I was wondering if anyone could give me pointers what could cause "named" to be down automatically simultaneously on both primary and secondary DNS servers. Individually each of the servers function properly. So, there should be some event (which got unlogged) which trigerred both servers to shut down "named"?
There was nothing abnormal in the log files. Also, "named" was down on both primary and secondary DNS servers on each occasion.
Thanks Tony
- : 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
Try running something like this:
# named -d 255 -u named -g > ~/named.log 2>&1 &
(note that you need a user called 'named' for that to work)
The next time named crashes, take a look at the last few lines of ~/named.log and see if it gives you any clue as to where the problem is. You can always turn up the debug level (the 255) to get more information about what is going on.
~Bradley - : 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
