Description of problem: After restarting LDAP server, dyndb-ldap module cannot connect (or reconnect) to LDAP server. I think that ldap module guess, that connection is still alive, but it dont be. from named.log: named[5306]: bind to LDAP server failed: Can't contact LDAP server ...message are inserted repeatly after every incoming DNS query and all DNS responses had SERFAIL status. If I also restart named daemon after restarting LDAP server, all is OK and ldap module successfuly creates new connection. Version-Release number of selected component (if applicable): bind-utils-9.6.1-4.P1.fc11.x86_64 bind-dyndb-ldap-0.1.0-0.3.a1.fc11.x86_64 bind-libs-9.6.1-4.P1.fc11.x86_64 bind-9.6.1-4.P1.fc11.x86_64 openldap-servers-2.4.15-3.fc11.x86_64 How reproducible: Steps to Reproduce: 0. precondition: running ldap server 1. start named daemon with configured ldap storage for dns zones 2. restart ldap server 3. try to query some dns record that is stored in ldap directory, the result is always SERVFAIL Actual results: Expected results: Additional info: If I try to query the same hostname after step 3, that I queried after step 1, I got the correct DNS response from named, because I thnik, ldap module uses cache for latest queried dns records. But all other non-cached records will never be translated.
Michal, I'm afraid I won't be able to fix this as fast as the previous issue, I'm probably going to need more thorough testing. There actually is a reconnection logic, but it seems that it doesn't work very well. For now, I opened a new ticket upstream at https://fedorahosted.org/bind-dyndb-ldap/ticket/20 to make sure I fix this before releasing beta. I hope that this bug doesn't cause you much trouble. You are right that some records get cached, but they will still get discarded after some time (configured through the cache_ttl option in seconds).
No problem, it is not so important problem. I am using this module only for a while because I have it accidently found in yum search ldap command :) and I used it for testing instead of bind-sdb module (I have interest on dyn updates, but I dont use it now). I have using LDAP only for internal organization records and some downtime is not critical, mostly only for my information of running workstations. Critical records I have still stored in files, ... I will waiting for later updates of this module and maybe I will move all records into LDAP in future :). Thank you for your work on this module :)
bind-dyndb-ldap-0.1.0-0.4.a1.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/bind-dyndb-ldap-0.1.0-0.4.a1.fc11
New build with fixes is ready. Please let me know if this helps.
Yes, I can confirm, that this update have successfuly reconnect to LDAP after LDAP server restarting. Thank you.
bind-dyndb-ldap-0.1.0-0.4.a1.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bind-dyndb-ldap'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-9372
bind-dyndb-ldap-0.1.0-0.4.a1.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.