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
[Pdns-users] Status of the LDAP backend in 3.0 release
People, Unless something happens, the LDAP backend will move to 'unmaintained' status in the 3.0 release. Please read below for the how and why of this, and what could possibly be done to change this. The brief version is that someone will have to step up to maintain the LDAP backend, or a PowerDNS user will have to fund us to do so. But see below for more background on how PowerDNS development happens. On Wed, Mar 23, 2011 at 10:10:13AM +0200, Nick Milas wrote: I always hope that a developer can sometime provide fixes for these, [LDAP issues] esp. 260 313 which are bugs (and not feature requests). To clarify, PowerDNS development happens because one or more of the following three reasons: 1) We think something has wide utility, or is good for the internet or DNS, and should be in PowerDNS. 2) There are people in the PowerDNS community developing maintaining it. 3) There are end-users with support contracts that need it, or there are end-users willing to fund the development directly. (there are also some other reasons, for example, we sometimes build features for users in return for other things they have done for us, sort of an open source exchange of favours. Part of PowerDNSSEC happened in this way. We also develop quite some things because, frankly, we find them cool) For LDAP, right now none if these things is the case. 1) We don't feel that LDAP is a particularly good or interesting place to store DNS data. It will for example have big problems with PowerDNSSEC because of lack of ordering. 2) We thank Norbert for his years of maintenance, but apparently he feels the same way, or at least has no time. But he did a great job. 3) Finally, nobody has come forward with more than 'hope' that we'd restart work on the LDAP backend (ie, support contracts or funding). If we spend time on LDAP, we don't spend it on something else unless we hire more help. And as long as '3' is not the case, that won't happen. It may be good to realise that almost all big new PowerDNS features (TSIG, (Power)DNSSEC, Lua filtering, DNS64) have been made possible by PowerDNS users funding the development. So, unless something changes, we will only make sure that OpenLDAP keeps compiling, and to merge patches submitted by the community. The documentation will be updated to this effect, and so will the 3.0 release notes. 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)? What you are probably seeing is that the level of 'care' for LDAP is not quite there. I don't think the OpenLDAP developers would be interested in maintaining one of their dependencies. So while I feel your pain, and I'm not happy about it, for now this is the way it is going to be, unless someone steps up to either maintain the LDAP backend, or comes up with some funding to do so. Kind regards, Bert Hubert PowerDNS ___ 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] Status of the LDAP backend in 3.0 release
On 23/3/2011 11:05 πμ, bert hubert wrote: Unless something happens, the LDAP backend will move to 'unmaintained' status in the 3.0 release. I think this attitude is the best. At least new admins planning DNS server deployment *will know* that they should probably keep off LDAP backend, since it's unmaintained. My opinion is that LDAP backend is a very good solution for (at least) small-to-mid sized organizations which can store/manage/use in a DIT all their data and use standard admin tools, and this backend should be maintained, but you are right: Since no direct interest is expressed (which I still find surprising), there is no other way to go. Pitty I am not a (professional) developer and my organization doesn't have the resources to invest in improving an already good (as I think) piece of software. We'll have to live with the current version and probably migrate to other backend later - unless things change. Maybe some people/organization will continue to find LDAP backend cool enough to give it a push. :-) Thanks, Nick ___ Pdns-users mailing list Pdns-users@mailman.powerdns.com http://mailman.powerdns.com/mailman/listinfo/pdns-users
