bind 8.4.1 under windows stopping without warning

Danny Mayer mayer at gis.net
Wed Sep 24 22:55:58 UTC 2003


At 05:06 PM 9/24/03, ree at thunderstar.net wrote:

>Thanks for the suggeestion, Danny - the only reason I haven't done that
>already, though, is the unresolved (or what I though were unresolved)
>problems running bind 9 under Windows such as the too many open files bug

Fixed in 9.2.3rc1 and later. This is the long promised rewrite. BIND 8
still has the problem.

>and another issue with a similar symptom to what I describe below where
>named stops suddenly, requiring manual restarts.

See above.

>Are these things resolved for the most part - ie - would you say it is
>workable to run bind 9 on windows in a production environment?

Yes. That's for you to judge. Most people report much better reliability.

Danny

>Thanks!
>
>On Wed, 24 Sep 2003, Danny Mayer wrote:
>
> > Upgrade to 9.2.3rc3 and see if the problem still arises. BIND 8 on
> > Windows still has some architectural problems with sockets.
> >
> > Don't use rc4, as the build was bad.
> >
> > Danny
> > At 11:47 PM 9/23/03, ree at thunderstar.net wrote:
> > >I am wondering if anyone can shed some light on something I recently
ran
> > >into with a windows server running bind 8.4.1 (same behavior also noted
on
> > >8.3.4).
> > >
> > >The exact scenario is a server that is secondary for a few thousand
zones.
> > >When a few hundred of these were removed from the server, resulting in
> > >numerous attempts by the secondary to transfer those zones, which, of
> > >course, errored out since the primary was no longer authoritative, bind
on
> > >the secondary would stop suddenly several times per day.
> > >
> > >I was in the midst of removing a bunch of zones but I didn't do the
> > >secondary at the same time as the primary. As soon as the primary had
> > >those same zones removed, no more sudden stops.
> > >
> > >The server is running NT4.
> > >
> > >Obviously, one shouldn't have many zones in a secondary for which the
> > >primary is not authoritative, however, bind shouldn't stop due to this
> > >either.
> > >
> > >TIA
> > >
> > >
> >
> >




More information about the bind-users mailing list