[Pdns-users] Status of the LDAP backend in 3.0 release

Nick Milas nmilas at admin.noa.gr
Sun May 29 15:28:06 UTC 2011

I am sending this message as an update and a wrap-up for the LDAP backend:

Bug 313 (ldapbackend sets TZ to UTC but should not) is fixed (according 
all test reports).

Bug 260 (LDAP backend doesn't try to reestablish connection once lost) 
will be fixed by Bert (I thank him in advance).

[Bug 37 (old, closed)]:
In the meantime I found that pdns_control  does not work with the LDAP 
Backend to send Notify messages (although it should, according the 
documentation). I have asked Bert, if he can, to kindly take a look in 
that too (when he looks into Bug 260 above, but he has not replied); 
this should be important for the completeness of PDNS with LDAP backend 
(see bug 37). Yet it's not crucial, thanks to third-party software: 
which works (this is what I am currently using).

Ticket #318 (Master (Notify) functionality with ldap backend):
Up to now, I was thinking that the absence of trigger support in LDAP 
was a reason why Master (Notify) functionality had not been included in 
the LDAP backend. Yet, as Fredrik Danerklint (of the MongoDB backend, 
whom I thank) has informed us, no triggering support is needed, because 
PDNS periodically asks the backends for fresh zones, providing them with 
a list of previously 'notified_serials'. So, it should be trivial (by 
any developer) to extend the backend so as to identify changed serials 
and create a list of changed zones (as required for the Master 
Volunteers wanted.

No ticket: DNSSEC support
It will need Developer(s) with DNSSEC knowledge! Backend (LDAP) Server 
capabilities should not pose insurmountable obstacles.
Volunteers wanted.


More information about the Pdns-users mailing list