<p>If we also replace the object class used to get the DNS related
attributes to one allowing these attributes to be combined with the
-dhcpHost object class, we can merge the DNS and DHCP entries into one.
+dhcphost object class, we can merge the DNS and DHCP entries into one.
I've written such object class in the dnsdomainaux.schema file (need
proper OIDs, but that is a minor issue), and tested the setup. It
seem to work.</p>
this:</p>
<blockquote><pre>
- dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,\
-dc=no
+ dn: cn=hostname,cn=group1,cn=THINCLIENTS,cn=DHCP Config,dc=skole,dc=skolelinux,dc=no
cn: hostname
- objectClass: dhcpHost
+ objectClass: dhcphost
objectclass: domainrelatedobject
- objectclass: dnsDomainAux
+ objectclass: dnsdomainaux
associateddomain: hostname.intern
arecord: 10.11.12.13
- dhcpHWAddress: ethernet 00:00:00:00:00:00
- dhcpStatements: fixed-address hostname
- ldapConfigSound: Y
+ dhcphwaddress: ethernet 00:00:00:00:00:00
+ dhcpstatements: fixed-address hostname
+ ldapconfigsound: Y
</pre></blockquote>
<p>The DNS server uses the associateddomain and arecord entries, while
-the DHCP server uses the dhcpHWAddress and dhcpStatements entries
+the DHCP server uses the dhcphwaddress and dhcpstatements entries
before asking DNS to resolve the fixed-adddress. LTSP will use
-dhcpHWAddress or associateddomain and the ldapConfig* attributes.</p>
+dhcphwaddress or associateddomain and the ldapconfig* attributes.</p>
<p>I am not yet sure if I can get the DHCP server to look for its
-dhcpHost in a different location, to allow us to put the objects
+dhcphost in a different location, to allow us to put the objects
outside the "DHCP Config" subtree, but hope to figure out a way to do
that. If I can't figure out a way to do that, we can still get rid of
the hosts subtree and move all its content into the DHCP Config tree