[bind10-dev] LDAP in BIND 10 (was: SQL in BIND 10)

[JINMEI Tatuya / 神明達哉]

At Mon, 08 Apr 2013 11:56:34 +0200,
Petr Spacek <pspacek at redhat.com> wrote:

> later messages in thread 'SQL in BIND 10' called for real-world requirements 
> and use cases for SQL backends in BIND. I'm 2 months late, but I will add one 
> real-world case where LDAP database is used as backend for BIND 9.

Thanks for sharing the usage.  It's interesting and informative.

Some quick comments in the context of BIND 10:
- one big missing piece (other than handling LDAP API) for supporting
  this type of use is the asynchronous notification/pull mechanism to
  incorporate changes to the LDAP DB.
- where to store other zone related data (or a kind of config) such as
  per zone ACLs is one open question.  but your use case is
  interesting in that some users want to manage it outside of the
  nameserver's configuration.
- I don't know if startup time is important for you, but in BIND 10 it
  would still be possible to minimize it once we complete the current
  shared memory support: the latest memory image is saved in a
  memory-mappable file.  when BIND 10 starts it would map the file into
  memory, check the LDAP data, and only apply the diffs between the
  saved in-memory data and the latest DB data (if the diff can be
  easily retrieved, e.g., by specifying the old version of zone SOA).

---
JINMEI, Tatuya
Internet Systems Consortium, Inc.