From: Petter Reinholdtsen <pere@hungry.com>
Date: Sat, 17 Jul 2010 18:52:43 +0000 (+0000)
Subject: Improve text and HTML.
X-Git-Url: http://pere.pagekite.me/gitweb/homepage.git/commitdiff_plain/066daca9d59eaabff754d6a808a0da0360f76087?ds=sidebyside

Improve text and HTML.
---

diff --git a/blog/draft/2010-07-03-ldap-searches.txt b/blog/draft/2010-07-03-ldap-searches.txt
index 554027a7ab..4a6b450e0f 100644
--- a/blog/draft/2010-07-03-ldap-searches.txt
+++ b/blog/draft/2010-07-03-ldap-searches.txt
@@ -1,6 +1,6 @@
 Title: What are they searching for - PowerDNS and ISC DHCP in LDAP
 Tags: english, debian, debian edu, nuug, ldap
-Date: 2010-07-17 20:00
+Date: 2010-07-17 21:00
 
 <p>This is a
 <a href="http://people.skolelinux.org/pere/blog/Time_for_new__LDAP_schemas_replacing_RFC_2307_.html">followup</a>
@@ -272,12 +272,15 @@ really help when the DHCP subtree need to have a fairly fixed
 structure.</p>
 
 <p>Based on the observed behaviour, I suspect a LDAP structure like
-this might work:
+this might work:</p>
 
 <blockquote><pre>
 ou=services
   cn=dns-and-dhcp (dhcpService) - dhcpServiceDN points here
     cn=dhcp (dhcpServer)
+    cn=dhcp-internal (dhcpSharedNetwork/dhcpOptions)
+      cn=10.0.2.0 (dhcpSubnet)
+        cn=group1 (dhcpGroup/dhcpOptions)
     cn=dhcp-thinclients (dhcpSharedNetwork/dhcpOptions)
       cn=192.168.0.0 (dhcpSubnet)
         cn=group1 (dhcpGroup/dhcpOptions)
@@ -285,8 +288,13 @@ ou=services
       cn=hostname (dhcpHost/domainrelatedobject/dnsDomainAux)
 </pre></blockquote>
 
+<P>This is not tested yet.  If the DHCP server require the dhcpHost
+entries to be in the dhcpGroup subtrees, the entries can be stored
+there instead of a common machines subtree, and the PowerDNS base
+would have to be moved one level up to the dns-and-dhcp subtree.</p>
+
 <p>The combined object under the machines subtree would look something
-like this:
+like this:</p>
     
 <blockquote><pre>
 dn: dc=hostname,ou=machines,cn=dns-and-dhcp,dc=skole,dc=skolelinux,dc=no