[Pdns-users] pdns 3.1-pre & pdns_control notify

GAVARRET, David david.gavarret at sfr.com
Mon Jan 30 13:58:16 UTC 2012


For my reverse authoritative servers, I'm using the pdns 3.1-pre release with a combination of a gmysql backend plus a custom one (my custom backend answers with generic response when a specific PTR is not found in the database).

After some manual updates, I tried to use the "pdns_control notify" command to send NOTIFY to 3rd part slave server (in my case, RIPE nameserver), but I can't see any notification going out of my server (tcpdump only shows requests coming from slave servers, not concerning the zone I try to notify), even if pdns seems to have taken into account my command :
Jan 30 14:26:40 ... pdns-reverse[29151]: Notification request for domain '7.109.in-addr.arpa' received from operator
Jan 30 14:26:40 ... pdns-reverse[29151]: Queued notification of domain '7.109.in-addr.arpa' to

Are there any special conditions before a notification is sent ? Are there any means to see content of the queue ?
As I see the correct IP address of the nameserver in the log, I think that my setup and my custom backend is not a problem (previously my chrooted setup was incorrect and I could see some errors "nameservers do not reverse!"). What should I check to be sure my setup is not in default ?

Thanks in advance,

King regards,

David Gavarret

More information about the Pdns-users mailing list