On Tuesday 15 May 2007 05:56, Florian Weimer <[EMAIL PROTECTED]> wrote: > * Russell Coker: > > I don't know how to reproduce it. It's quite likely that it happened in > > response to a DOS attack. > > Okay, so this is not an ongoing issue for you?
No. > There are quite a few similar bug reports, for magic byte mismatches, > and I'm not sure what to do with them. Perhaps patching in some kind > of backtrace logging facility, so that we've got more data. But if > it's random memory corruption due to flaky RAM or some internal race > condition in BIND code which causes this problem, this is not likely > to shed any light on the issue. Probably the best thing to do would be to have BIND SEGV in such situations. With a core file you should be able to track it down. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
