Following the thread on this list, I upgraded bind to patch level 5 on
several Unix machines (some from source RPM (rawhide), some from pure
source (from bind's home page)).
Since then named consumes 60-100% of CPU. Right after startup it uses 100%
CPU and it is extremely slow to respond (so much so that sometimes
nslookup times out). After a few minutes the utilisation drops a little
bit (60-80%), and it starts answering quesries in a timely manner.
Has anyone else seen this? Is it a problem with patch level 5? Or we
happen to be targetted for some strange DoS (or flood or whatever) attack?
Hossein
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
