Thread handling

[Evan Hunt]

> Regarding the child process(es), does named create one child process,
> or can it be multiple processes? I assume each process loads the
> shared objects for itself, so only one call to dns_dlzcreate per
> process?

I'm pretty sure it's called only once on startup, after daemonizing,
and again whenever you reconfigure the server.  (I haven't checked,
but I think that's the case.)

> Question about the cache mentioned here. Can cache be configured to
> pull from a DLZ?

No.

> As far as I know, the DynDB API is not merged to BIND's codebase yet.

BIND does have dyndb support, since 9.11.

As far as I know, though, the only two dyndb modules in existence are
the bind-dyndb-ldap modiule that was written by Red Hat as part of
FreeIPA, and a toy module used for testing.  If you were interested in
writing your MongoDB module for dyndb instead of DLZ, I'd be quite
excited about that, I've long hoped the API would get more use.

> In the absence of that, is caching from DLZ a possible configuration
> on a single BIND server?

Not DLZ, no. And I'm not sure dyndb can be used for the cache database,
either; do you know something about it that I don't?

It would definitely be easier to *make* dyndb work for the cache;
it has all the necessary API calls, and DLZ doesn't. But I don't
know a way to configure it to take the place of the cache currently.
If you do, please educate me.

-- 
Evan Hunt -- each at isc.org
Internet Systems Consortium, Inc.