named has a week long fault tolerance?
I have a webserver whose named daemon failed today. It would also refuse to restart properly.
I discovered the fault from the debug log, and it was a double entry for a certain domain in named.conf. It's running OK now. However, that double entry had been there for a full week, and named had been started several times since then. My impression is that it tolerated the fault for a week and then lost its patience, and said "well, he still hasn't corrected it .. I have to show him who's boss now" KAPLUNK!, and down it goes. But - I ask myself - why fail now,a nd not several days ago when the faulty named.conf was read for the first time. Anybody any ideas? |
well, not too much interest in this. I suppose it's a webmaster type question.
One thing I will add, is that I'm almost sure named was down, and yet my domain-names were being served. Impossible? Well, then it was also impossible that "named" was running with a faulty named.conf. So both avenues are impossible. It all points to some other process that was doing named's work. |
All times are GMT -5. The time now is 09:02 AM. |