Hello Tom, On Jul 20, 2012, at 9:31 , Tom Bamford wrote:
> I encountered an issue with the way the ldapbackend performs AXFR > searches. It assumes that your subdomain entries are children of the > parent dn of the entry with your SOA record. > > Accordingly, I have patched ldapbackend.cc (ldapbackend.so) to use the > ldap-basedn that I defined rather than the parent dn from the first > AXFR related search. Rather than change the current behaviour, I also > added a boolean configuration item ldap-basedn-axfr-override which is > first evaluated using mustDo(). > > It's a simple change but I expect could be very useful to other admins > in a use case similar to mine, where your LDAP tree is not designed > solely for DNS and you might have host entries outside the same parent > DN as your sOARecord. Diff is attached for a patch against the current > trunk (also also works for 3.1.1 and 3.0.1, also 2.9.22 when applied > manually). Good to hear the ldapbackend is seeing usage, we don't hear much of that! Thank you for your patch; would you please file a ticket at wiki.powerdns.com and attach it? Otherwise, we are likely to forget. Thanks! Kind regards, -- Peter van Dijk Netherlabs Computer Consulting BV - http://www.netherlabs.nl/ _______________________________________________ Pdns-dev mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-dev
