Security Incidents mailing list archives
BIND 9.2.1 crashes
From: Benjamin Franz <snowhare () nihongo org>
Date: Sun, 5 Oct 2003 14:06:34 -0700 (PDT)
This is going to necessarily be sketchy on details because I don't have
many.
In the last 48 hours I've had two nameservers on completely seperate
subnets crash with no indication as to what crashed them. Both nameservers
are running BIND 9.2.1 (One system is running RH 7.3, BIND 9.2.1-1.7x.2.
The other system is running RH 7.2, BIND 9.2.1-1.7x.2).
The named on the RH7.3 system 'tied itself in a knot' without formally
dying - it just stopped doing name service after a lot of 'no more
recursive clients: quota reached' messages (related to a maillist mailing
I believe initially - but this had stopped before I was called in - at
which time the named was still refusing service, but hadn't logged
anything in 40 minutes). The named on the RH7.2 system completely died
with no logged messages at all about 18 hours after the RH7.3 system
problem, with no unusual activity preceding its death - it just stopped
for no apparent reason).
The 7.2 system has been running for several months with no issues. The 7.3
system was brought online a week ago - and had no trouble until this.
Has anyone else been seeing BIND crashes on previously stable systems in
the last week?
--
Benamin Franz
Gauss's law is always true, but it is not always useful.
-- David J. Griffiths, "Introduction to Electrodynamics"
---------------------------------------------------------------------------
----------------------------------------------------------------------------
Current thread:
- BIND 9.2.1 crashes Benjamin Franz (Oct 06)
- <Possible follow-ups>
- Re: BIND 9.2.1 crashes Keith Bergen (Oct 06)
- Re: BIND 9.2.1 crashes jlewis (Oct 06)
- Re: BIND 9.2.1 crashes Benjamin Franz (Oct 06)
- RE: BIND 9.2.1 crashes LordInfidel (Oct 07)
- RE: BIND 9.2.1 crashes Benjamin Franz (Oct 07)
