On 1.4.2015 07:51, Jorgen Lundman wrote:
Hmm, that might be a challenge. bind-dyndb-ldap code implicitly assumes that
there is 1:1 mapping between DNS name-LDAP DN. This makes implementation of
dynamic updates much easier.
Well, you weren't wrong there. :) I did try a few different
Hmm, that might be a challenge. bind-dyndb-ldap code implicitly assumes that
there is 1:1 mapping between DNS name-LDAP DN. This makes implementation of
dynamic updates much easier.
Well, you weren't wrong there. :) I did try a few different solutions,
first letting ARecord/NSRecord trickle
Hmm, that stinks! I would be happy to look into it if you can provide me with
output from a profiler of your choice. (It might be a good idea to profile
bind-dyndb-ldap together with whole named process to see all the
interactions.)
Hold those horses. I must admit this timing didn't sit
Hello Jorgen and list,
On 26.3.2015 01:25, Jorgen Lundman wrote:
Thanks for your email, (I have included the ML in this reply)
We run Solaris with bind+DLZ+ldap on the DNS servers, and are looking at
better performance. Which means evaluating bind-dyndb-ldap. I did some
minor tweaks to
Petr Spacek wrote:
Perfect! I can merge your changes upstream if you send me a patch with your
changes. It would make your life easier later when you need to pick new code.
Not a problem, I need to figure out why Solaris mkdir returns -1, with
errno = 0. Goes against the manpage and all
Thanks for your email, (I have included the ML in this reply)
We run Solaris with bind+DLZ+ldap on the DNS servers, and are looking at
better performance. Which means evaluating bind-dyndb-ldap. I did some
minor tweaks to compile bind-dyndb on Solaris.
Since we already have large systems
