Tomas,
It’s been a while since I’ve done it but I seem to remember it being relatively
straightforward to convert between OpenLDAP's and 389’s schema formats. Have you made
an attempt to convert the PowerDNS schema?
-morgan
On Sep 22, 2017, at 6:13 AM, Tomáš Brandýský
<tomas.brandysky(a)gmail.com> wrote:
Hello,
in our company we're working on project of migration multiple master-slave
synchronized OpenLDAP servers to multi-master 389 DS servers configuration.
We've been using OpenLDAP to store data of multiple applications such as DNS servers
(PowerDNS), DHCP servers, Mail servers (Postfix, Amavis) etc..for at least 9 years.
We need to use custom LDAP schemas to store the data of these applications in LDAP. These
need to be converted from OpenLDAP format to RFC strict 389 DS convenient format which
actually works great for most of them.
Unfortunately I didn't manage to use PowerDNS LDAP schema
(
https://doc.powerdns.com/authoritative/backends/ldap.html) with 389 DS. As I tried to
google more information why this schema doesn't work with 389 DS I found out it uses
'dnsdomain' schema which comes with OpenLDAP
(
https://lists.fedoraproject.org/pipermail/389-users/2011-January/012721.html) and was
removed from 389 DS many years ago.
Could you please give me some advice what can I do to make PowerDNS backend work with 389
DS ?
We're mid-sized company with many services using LDAP as their storage backend and to
migrate all of them to new LDAP servers is priority number one. If there is no way to
migrate PowerDNS LDAP data from OpenLDAP to 389 DS the whole project of migration to 389
DS would need to be reconsidered. Nevertheless I don't understand why such a worldwide
popular DNS server which PowerDNS surely is couldn't be used with 389 DS LDAP
implementation which is also quite popular.
Thank you
Tomas Brandysky
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org