Re: [Pdns-users] Heading up to PowerDNS Authoritative Server release 3.0: please check your open tickets
Good news about upcoming version. However, not so good news for the LDAP backend... So, I feel that LDAP-related issues should - at least - remain open, since they have not been fixed. Closing them with an indication of Unable to devote time to the LDAP backend (or similar), would most probably not promote true resolution (fix). I always hope that a developer can sometime provide fixes for these, esp. 260 313 which are bugs (and not feature requests). Would it help to request e.g. openldap developers with DNS background (through their mailing list) to possibly show interest in resolving them (since no one in pdns mailing list has volunteered and Norbert has stopped support)? Thanks, Nick On 22/3/2011 10:38 μμ, bert hubert wrote: Ticket #313 (ldapbackend sets TZ to UTC but should not) closed by ahu wontfix: we are currently unable to devote time to the LDAP backend. Ticket #260 (LDAP backend doens't try to reestablish connection once lost) closed by ahu wontfix: We are currently unable to fix LDAP issues. Ticket #298 (AXFR query fail with LDAP backend) closed by ahu wontfix: We are unable to address LDAP issues at this time. Ticket #318 (Master (Notify) functionality with ldap backend) closed by ahu wontfix: We are unable to enhance the LDAP backend. Ticket #323 (powerdns authoritative server with ldap backend hangs when ldap server is ...) closed by ahu wontfix: We are unable to fix LDAP issues. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Heading up to PowerDNS Authoritative Server release 3.0: please check your open tickets
Hi Nick, As nice as it would be to have unlimited development resources, that is never the case. Since no community member has stepped up to work on the LDAP backend and PowerDNS.com does not have funds to work on the LDAP backend, it is better to go ahead and mark them as closed/wontfix. If an enterprising LDAP developer ever appears, they can find them all and work on them and fix them just as easily as if they were open. Other than bug reports, there has been no ground-swell of LDAP support either with development time or funds. That is pretty indicative of its relative importance compared to the more traditional SQL, Bind and pipe backends. Regards, Ken On Wed, Mar 23, 2011 at 10:10:13AM +0200, Nick Milas wrote: Good news about upcoming version. However, not so good news for the LDAP backend... So, I feel that LDAP-related issues should - at least - remain open, since they have not been fixed. Closing them with an indication of Unable to devote time to the LDAP backend (or similar), would most probably not promote true resolution (fix). I always hope that a developer can sometime provide fixes for these, esp. 260 313 which are bugs (and not feature requests). Would it help to request e.g. openldap developers with DNS background (through their mailing list) to possibly show interest in resolving them (since no one in pdns mailing list has volunteered and Norbert has stopped support)? Thanks, Nick On 22/3/2011 10:38 , bert hubert wrote: Ticket #313 (ldapbackend sets TZ to UTC but should not) closed by ahu wontfix: we are currently unable to devote time to the LDAP backend. Ticket #260 (LDAP backend doens't try to reestablish connection once lost) closed by ahu wontfix: We are currently unable to fix LDAP issues. Ticket #298 (AXFR query fail with LDAP backend) closed by ahu wontfix: We are unable to address LDAP issues at this time. Ticket #318 (Master (Notify) functionality with ldap backend) closed by ahu wontfix: We are unable to enhance the LDAP backend. Ticket #323 (powerdns authoritative server with ldap backend hangs when ldap server is ...) closed by ahu wontfix: We are unable to fix LDAP issues. ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
Re: [Pdns-users] Heading up to PowerDNS Authoritative Server release 3.0: please check your open tickets
On Tue, 22 Mar 2011 21:38:30 +0100, bert hubert wrote: The big 3.0 release is coming real close, and it is going to be a big one. For the 'work in progress' release notes, please see http://doc.powerdns.com/changelog.html#changelog-auth-3-0 Just wanted to check what the status is on having a PowerDNS master with a non-PowerDNS slave for DNSSEC signed zone - we had briefly discussed this some time ago and I think the slave (if it's not PowerDNS) currently won't do an AXFR when the RRSIG changes (and the SOA won't change automatically). Will this be supported in the 3.0 release? Christof -- http://cmeerw.org sip:cmeerw at cmeerw.org mailto:cmeerw at cmeerw.org xmpp:cmeerw at cmeerw.org ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
