[nsd-users] Multiple consumer catalog zones support in NSD
Jeroen Koekkoek
jeroen at nlnetlabs.nl
Mon Oct 28 14:48:08 UTC 2024
Hi Guillaume-Jean,
Sorry for not getting to this sooner! It escaped my attention. Willem's
the one who implemented it, but I believe this can be changed by means
of an undocumented compile time define
(MULTIPLE_CATALOG_CONSUMER_ZONES). At which point multiple consumer
zones are supported.
Note that it may cause problems if a member zone occurs in multiple
consumer zones though, which is why the define is there.
Hope that answers your question?
Best regards,
Jeroen
On Wed, 2024-10-23 at 07:52 +0200, Guillaume-Jean Herbiet via nsd-users
wrote:
> Hello,
>
> The NSD documentation on Catalog zones[1] states:
>
> > NSD can be a producer of catalog zones as well as a catalog zone
> > consumer, but it is limited to process only a single consumer zone.
>
> This can be a shortcoming in some architectures, like when NSD is
> used as a distribution server, dynamically "collecting" domains from
> several primary servers (each with its own catalog zone) and further
> transferring them to public authoritative servers.
>
> How hard is this limitation? Is it deeply rooted in NSD internals or
> is there the possibility that the code could evolve to supporting
> multiple producers AND multiple consumer zones ?
>
> Regards,
>
>
> [1]
> https://nsd.docs.nlnetlabs.nl/en/latest/catalog-zones.html#catalog-zones
>
> --
> Guillaume-Jean Herbiet
>
More information about the nsd-users
mailing list