From: Petter Reinholdtsen Date: Fri, 16 Jul 2010 22:19:28 +0000 (+0000) Subject: More text. X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/18922b3170c3e223546e70f25281f3124cda9406 More text. --- diff --git a/blog/draft/2010-07-03-ldap-searches.txt b/blog/draft/2010-07-03-ldap-searches.txt index 276cfb5bc9..7e33251be1 100644 --- a/blog/draft/2010-07-03-ldap-searches.txt +++ b/blog/draft/2010-07-03-ldap-searches.txt @@ -1,9 +1,12 @@ Title: What are they searching for - PowerDNS and ISC DHCP in LDAP -As a step to try to see if it possible t to merge the DNS and DHCP -LDAP objects for compters in Debian Edu, I have had a look at how -pdns-backend-ldap and dhcp3-server-ldap use the LDAP server. The two -approaches are quite different. +

This is a followup on my previous work on merging all the computer +related LDAP objects in Debian Edu.

+ +

As a step to try to see if it possible to merge the DNS and DHCP +LDAP objects, I have had a look at how pdns-backend-ldap and +dhcp3-server-ldap use the LDAP server. The two implementations are +quite different and use LDAP in two different ways.

To get this information, I started slapd with debugging enabled and dumped the debug output to a file to get the LDAP searches performed @@ -205,8 +208,21 @@ search with "cn=DHCP Config,dc=skole,dc=skolelinux,dc=no" as the base and "(&(objectClass=dhcpHost)(dhcpHWAddress=ethernet 00:00:00:00:00:00))" as the filter. - - +Conclusion +========== + +The PowerDNS implementation seem to be very flexible when it come to +which LDAP schemas to use. Its "tree" mode is rigid when it come to +the the LDAP structure, while its "strict" mode is very flexible, +allowing DNS objects to be stored anywhere under the base cn specified +in the configuration. + +The DHCP implementation on the other hand is very inflexible, both +regarding which LDAP schemas to use and which LDAP structure to use. +I guess one could implement ones own schema, as long as the +objectclasses and attributes have the names used, but this do not +really help when the DHCP subtree need to have a fairly fixed +structure. SRCH "dc=skole,dc=skolelinux,dc=no" 2 0 0 0 0 filter: (&(objectClass=dhcpServer)(cn=dhcp))