Comment # 6 on bug 1204466 from William Brown

The issue is there is very little desire and interest to integrate YaST with
LDAP.  It's in the process of being removed (
https://github.com/yast/yast-users/pull/366 ).

Currently the way to do this is to use the 389-ds tools directly/manually.
Saying this, generally DHCP and DNS in ldap is "not a good idea" (dhcp
especially, and I'd know, I wrote part of the support for isc-dhcpd to work
with ldap and learnt my lessons the hardway). DNS also is very difficult
because LDAP doesn't have structured datatypes in a way that DNS really needs. 

So LDAP is good to go when it comes to users and group management, but using it
to create an IPAM is probably not a good way to progress. 

Saying this as well, LDAP is very hard to use by modern standards. 389-ds
certainly makes this a lot easier over openldap, but there are alternatives you
could consider (lldap, kanidm) if you want something small. 

Sorry about that,