At 11:44 PM 11/6/2004, Vinny Abello wrote:
>Anyone else experience this with BIND 9.3.0 on Windows 2003?
>
>Faulting application named.exe, version 0.0.0.0, faulting module ntdll.dll,
>version 5.2.3790.0, fault address 0x00008a3c.
>
>
>No other more descriptive errors in the event log and nothing in the BIND
>logs. This is the first time this has happened and BIND 9.3.0 has been
>running nonstop on a total of three like servers. I haven't run it in the
>foreground with debugging levels raised and waited for it to crash, no...
>it'd probably take several weeks or longer if it would happen again.
>
>Just curious if anyone else has experienced this particular problem.


About the only way to figure this out is to rebuild BIND in debug mode and
run it under the debugger and wait for it to fail. The debugger will show
you where it failed. Unfortunately this is not an option for most people.
The above error message is just not enough to figure out even where there
was a problem with the code.

Danny

>Vinny Abello
>Network Engineer
>Server Management
>vinny@tellurian.com
>(973)300-9211 x 125
>(973)940-6125 (Direct)
>PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A
>
>Tellurian Networks - The Ultimate Internet Connection
>http://www.tellurian.com (888)TELLURIAN
>
>There are 10 kinds of people in the world. Those who understand binary and
>those that don't.
>