bind-dyndb-ldap caching

[brendan kearney]

i am using the bind-dyndb-ldap plugin on my internal authoritative dns
servers, and have found that there is little to no caching going on in
bind.  i am looking to understand if this is misconfiguration on my
part, or if this is a functional tradeoff when using a ldap backend.

when i delete the previous "rndc stats" output file and then run the
command to get the latest output, i can see that cache hits and many
other cache related stats are 0.  i am wondering if is expected
behavior.

i am attaching the "rndc stats" output from my 3 internal bind
servers, and the same output from a caching recusrive resolver that
all clients are configured to use.  the 3 internal servers show little
to no caching, while the recursive resolver shows many cache hits.
the configs between all 4 instances are very similar, and nothiing
stands out as specifically implementing caching in the recursive
instance.

would there be any insight as to what i might be doing wrong or not
doing, that is causing the lack of caching on the instances that use
bind-dyndb-ldap?

thanks,

brendan