single class B zone vs multiple class C zone

Kevin Darcy kcd at daimlerchrysler.com
Fri May 25 22:18:27 UTC 2001


Yes, you may run into performance issues, since the zone will be larger and
probably change more frequently. This will greatly increase your zone-transfer
overhead. On the other hand, it may reduce your serial-number-query overhead,
since there are now less zones for the slave to check. But the
serial-number-query overhead is usually a small fraction of the zone-transfer
overhead, so you'll probably lose more than you'll gain here,
performance-wise.

Why do you care to consolidate all of those reverse zones? If you're
maintaining the data in those zones automatically via Dynamic Update from your
DHCP server, then it shouldn't really matter whether they are separate zones
or all one zone.


- Kevin

Hannah O Day wrote:

> I have both dhcp and ddns servers (BIND4.93) that run on Aix boxes.  I have
> been config all reverse zones on the per class C subnet basis.  I'm now
> upgrade the server to BIND8.2.3.  I want to config the reverse with only
> one class B instead of many class Cs.  Could anyone tell me if this will
> cause any performance issues since the updates will now happen to the
> entire class B instead of class c?





More information about the bind-users mailing list