This is related to ticket 211 which adds support for masters on non-standard ports:
With the changes in that ticket, PowerDNS will accept the NOTIFY messages, but it would then attempt to do an SOA check on port 53 from the IP address that sent them. This of course does not work. :)
The attached patch changes the server so that it will use the port defined for the master as the target of the SOA check. (Note that it only does this for the SQL backend, and not the BIND backend. I don't think the BIND backend supports masters on non-standard ports.)
The ''right'' way to do this is probably to have the SOA check be handled in the code that performs the XFR. That way a NOTIFY would simply schedule an immediate zone update rather than perform the SOA check. But the method here works.
Attachment '' (notify-accept.diff) https://gist.github.com/5466655
Attachment 'Incremental patch to apply after the patches in ticket #211' (notify-accept-incremental.diff) https://gist.github.com/5466656
Oh, forgot to attribute this. You can send questions to the development list, or contact me directly at:
Shane Kerr [[BR]]
Presumably fixed when #211 got fixed in PowerDNS 3.0.