> -----Original Message----- > From: Danny Mayer [mailto:[EMAIL PROTECTED] > Sent: Friday, September 05, 2008 9:22 PM > To: Vinny Abello > Cc: bind-users@isc.org > Subject: Re: BIND 9.4.2-P2-W1 stops responding > > > Well, that had no effect. Still seems to die pretty frequently. I > can't easily catch and restart BIND every 30 minutes so I'm going to > have to replace this server with a different one running an operating > system that behaves better with BIND. I already did this on my other > two name servers. If you have any other ideas or reasons I shouldn't > abandon BIND on Windows, let me know while I can still test it. > > > > -Vinny > > > > It's very hard to tell. The code has been heavily stress tested to > ensure it does not die. Are any of your address DHCP supplied or are > they all fixed IP addresses. That could potentially have affects but I > haven't seen that be a problem in the latest code. There will also be a > 9.5.0-P2-W1 soon which has additional changes that may help but it's > hard to know without seeing details. Can you file a bug report on this > to [EMAIL PROTECTED] with details of your named.conf file, what you > are > seeing, netstat -an to see what sockets are open, vm used, handles and > threads, CPU information and O/S and anything else that might be > useful. > A dump file if you have one might also be helpful if you have one and > you can find it.
Hi Danny, I know it's been heavily stress tested, and technically, it doesn't die as in the process dying. :) But it stops responding to UDP queries. As far as my memory goes (I'd have to recreate it again), I still see it listening on UDP 53, but get no response. I'll have to verify that though. No DHCP is involved at all. There is no dump file either as it's not crashing. I'll try to file a formal bug report as I find time. Thanks! -Vinny
