Hi, recently we've had a number of incidents where named has stopped answering requests and is spinning the CPU. The only symptom we have been able find is that there are lots and lots of open sockets. We've been unable to find anything logged that would suggest that there is an issue. Has anyone else seen this type of behaviour? Cheers Steve