Kees Monshouwer

If you need more supplementary groups increase the RUID_MAXGROUPS value is your best option at this moment. Dynamic allocation of supplementary groups space sounds tempting but, is pretty complicated. Your...

Disabling the zone cache is most likely a workaround for your issue. Related #11416

Not only this will lead to inconsistencies between primary and secondaries. It may also result in inconsistencies between secondaries. Such inconsistencies are problematic because they interact badly with aggressive negative...

The problem here is concurrent updateZoneCache() runs.

I do not see why you need this. The api and autoprimary both add the zone to the zone cache. Adding a zone a second time will not help you...

I'm no fan of the "put it in flush" approach. Flush and add-zone have very different use cases. A separate add-zone endpoint to support cases like this might be an...

This is not helping, it is only adding more confusion. Notifying native zones is a valid use case for people who want to control the process themself.

Some backend implementations are actually using the case sensitive version of the query.

Bandwidth is one, but how is this affecting TSIG? d_maxchunkrecords is also max envelopes per TSIG record.

Some numbers about the performance would be nice. Since on top of losing compression this will also, more ore less, triple the number of transferred RRs for a zone.