How to allow over 65536 zones in bind 8.1.2

[bind at guangbin.interland.net]

Thanks for your kind response.

We knew that bind 8.2.1 and bind 8.2.2 can support over 64K zones. But we
tested our name server under bind 8.2.1 and bind 8.2.2, both of version 
took over 99% CPU for hours. Even the messages from named read:
Nov  5 14:35:01 dns4 named: named startup succeeded
I can't do any query from this server over 30 minutes.

Since bind 8.2.1 and bind 8.2.2 took too much CPUs, we have to continue to
use bind 8.1.2. But the problem is that it can suppot at most 64K zones.

Is this a bug of bind 8.2.1 and bind 8.2.2 and do you any patch to fix
the mad CPU usage probelm?

Thanks for your kind help!

G. Liu

On Fri, 5 Nov 1999, Cricket Liu wrote:

> Didn't see the original posting, but...
> 
> > > I'm running bind 8.1.2 and I'll have more than 64K zones in the name
> > > server. According to bind 8.1.2 CHANGES:
> > >
> > >  272.   [func]          The zone number is now unsigned, allowing up to
> > >                         65536 zones instead of the previous limit of
> > > 32768.
> 
> >From a more recent CHANGES file:
> 
> 412.   [bug]           we now support 2**24-1 (16M) zones. (need
> namespaces!)
> 
> That was before 8.2's release.  I'd recommend 8.2.2, though.
> 
> cricket
> 
> Acme Byte & Wire
> cricket at acmebw.com
> www.acmebw.com
> 
> Attend the next Internet Software Consortium/Acme Byte & Wire
> DNS and BIND class!  See www.acmebw.com/training.htm for
> the schedule and to register for upcoming classes.
> 
>