[Pdns-dev] LDAP backend/notification problems
Paul van Tilburg
paul at luon.net
Tue Nov 1 20:45:11 CET 2005
Hi,
I have patched my pdns 2.9.18-13sarge1 (Debian sarge) package to
include the code implementing getDomainInfo for the LDAP backend
as posted by Norbert Sendetzky:
http://mailman.powerdns.com/pipermail/pdns-dev/2005-October/000369.html
(addressing ticket 37: http://wiki.powerdns.com/projects/trac/ticket/37).
The 'no such domain' problem is solved, but I still have some
problems/questions:
* The SOA record in LDAP denotes serial 2005110103, however when getting
the record I get a different value that is always the same
(regardless whether I increment the serial in the LDAP record):
luon.net. 300 IN SOA sphere.luon.net. hostmaster.luon.net. 4294967295 3600 1800 604800 1800
* When I run pdns_control notify luon.net, I get correct log entries:
cube pdns[23432]: Notification request for domain 'luon.net' received from operator
cube pdns[23432]: Queued notification of domain 'luon.net' to 192.87.65.68
cube pdns[24228]: Removed from notification list: 'luon.net' to 192.87.65.68 (was acknowledged)
but 192.87.65.68 doesn't seem to receive any notifications (a bind9
server), nor does it seem that any packet is sent.
I am using the `tree' type LDAP setup, attempting to move my luon.net
domain running on bind9 to a PowerDNS/LDAP based setup. Any hints are
appreciated and if I should provide some more debug information, please
let me know.
Paul
--
Student @ Eindhoven | email: paul at luon.net
University of Technology, The Netherlands | JID: paul at luon.net
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181
More information about the Pdns-dev
mailing list