[Pdns-dev] RE: Extending the LDAP Backend - Slave replication

Norbert Sendetzky norbert at linuxnetworks.de
Sat Apr 19 14:44:27 CEST 2008

Hi Adrian

> Further on my efforts to extend the LDAP backend to allow some
> customisation of the schema used for finding an returning DNS records,
> I'm curious about how the slave replication process works.  Does the
> LDAP backend even support master/slave states?  If not, I wonder how
> much work would be involved in getting it to support it.

I think it's possible for the LDAP backend to support being a fully compliant 
master in the PowerDNS sense if the last_notified and notified_serial values 
are stored in an extended dnsdomain2 schema. It might be worth to talk to the 
Bind LDAP maintainer about a common schema and naming.

> You see, while our servers will be authoritative masters for one set of
> domains, people pay us to simply be an off-site slave server for the
> domains that they then host, so we need to be able to receive their
> updates, and insert that into our ldap database.  I'm willing to do the
> work to add this functionality, if necessary, but if there's code
> already in place that I can simply alter to work with my configurable
> schema, I'd be much happier :)

LDAP server doesn't support transactions so it would be a bad idea to let it 
act as slave for another name server. You would mess up your LDAP tree if 
something goes wrong.
Please use an additonal PowerDNS bind or SQL-based backend for this. More than 
one backend can be used at the same time.

OpenPGP public key

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://mailman.powerdns.com/pipermail/pdns-dev/attachments/20080419/94333bd0/attachment.bin

More information about the Pdns-dev mailing list