Task #11 — dnsZone schema support
Attached to Project — PDNS LDAPLast edited by Norbert Sendetzky (nose) - Sunday, 22 Apr 2007, 12:22am
| Feature Request | Low | ||
| Backend / Core | Normal | ||
| Assigned | 1.0 | ||
| Norbert Sendetzky (nose) | Undecided | ||
| All |  |
||
|
There is a different schema in use with some products. It would be nice to see this made optional, to work with those systems. The schema is : http://www.venaas.no/ldap/bind-sdb/dnszone-schema.txt and it is used by the BIND9 sdb ldap backend - http://www.venaas.no/ldap/bind-sdb/ That would help with migration for people who are already using this schema. ISPMan is one product that uses this schema to manage bind9 - there's a feature-request with them up at https://sourceforge.net/tracker/?func=detail&atid=358390&aid=1703226&group_id=8390 |
|||
Comments (3) | Attachments (0) | Related Tasks (0/0) | Notifications (1) | Reminders (0) | History |
Comment by Norbert Sendetzky - Thursday, 19 Apr 2007, 11:05pm
The PowerDNS LDAP backend uses the dnsdomain2 schema, which was also used by the Bind sdb backend in the beginning. Unfortunately, the SDB maintainer created a totally new dnszone schema afterwards and it differs from the dnsdomain2 schema in the most important parts so it's not an enhancement which can be integrated easily.
It's rather difficult being compatible with this without duplicating much code in the PowerDNS LDAP backend, but I will see what I can do in the future.
Norbert
Comment by Norbert Sendetzky - Sunday, 6 Apr 2008, 10:50pm
I've written a script for migrating the Bind LDAP entries to PowerDNS LDAP by creating an LDIF file for updating the LDAP tree. This isn't what you've requested but might be a starting point.
Norbert
Comment by Alejandro Escanero Blanco - Monday, 29 Nov 2010, 11:36pm
There are a problem with dnszone-migrate.schema:
LDAP: error code 65 - invalid structural object class chain (dNSZone/dNSDomain)
dNSZone have SUP top and I think must have SUP 'dNSDomain2'
Thanks