[Pdns-users] master receiving notifies from slave
Curtis Maurand
curtis at maurand.com
Fri Mar 10 15:29:17 UTC 2023
slave-renotify=no was set.
I changed the only-notify which wasn't set to only-notify= and
also-notify was set to also-notify=
Let's see what happens
On 3/9/23 02:26, Klaus Darilion via Pdns-users wrote:
>
> PDNS sends only NOTIFYs for SLAVE zones is slave-renotify is turned on
> (globally, or per zone in domainmetadata table).
>
> So, if your SLAVEs shoudl not send NOTIFYs make sure to disable
> slave-renotify.
>
> If a PDNS instance slaves zones from a master, but also acts as master
> to other slaves, then you can fine tune NOTIFYs.
>
> I use "only-notify=" (empty value to disable all implizit NOTIFYs).
> Further I use "ALSO-NOTIFY" domainmetadata settings to specify NOTIFY
> targets per zone.
>
> regards
>
> Klaus
>
> *Von:*Pdns-users <pdns-users-bounces at mailman.powerdns.com> *Im Auftrag
> von *Curtis Maurand via Pdns-users
> *Gesendet:* Donnerstag, 9. März 2023 00:06
> *An:* pdns-users at mailman.powerdns.com
> *Betreff:* [Pdns-users] master receiving notifies from slave
>
> Hello,
> I have a pair of powerdns servers running on a debian derivative
> equivalent to bullseye: Devuan chimaera. I am running pdns
> authoritative version 4.7.3 from the powerdns debian repo. Devuan
> does not use systemd. I'm using sysvinit. The upgrade removes
> /etc/init.d/pdns script which is not good nor can I find it in the
> sources even though the docs say it's in there. That's not really why
> I'm writing.
>
> The slave server is sending notifies for one, and only one slave
> domain maurand.com to the master and the master (a supermaster) is
> refusing them, but they are happening several times per second. Boths
> servers are behind NAT firewalls and that would be the reason for the
> private IP in the notify.
>
> Mar 8 16:34:30 sirius pdns[27219]: Received NOTIFY for maurand.com from 192.168.100.1 but we are primary (Refused)
> Mar 8 16:34:35 sirius pdns[27219]: Received NOTIFY for maurand.com from 192.168.100.1 but we are primary (Refused)
>
> On the master (208.105.217.26) I have:
>
> 52 | maurand.com | NULL | NULL | MASTER |
> 2023030804 | NULL | NULL | 50 | NULL |
>
> On the slave (208.105.219.27) I have:
>
> | 17 | maurand.com | 208.105.217.26 | 1678315385 | SLAVE
> | NULL | | NULL | NULL |
>
> As I was typing out my cry for help, here, I may have solved this by
> upgrading the master to 4.7.3 from version 4.4.1 (which is what is in
> the debian repos), but after the upgrade, I still received a few more
> notifies after the upgrade, but It seems to have settled down.
>
> I searched around the net for answers, but I can't find any. I've
> been running powerdns for a very long time. Does anyone have any
> ideas what might be causing this?
>
> Thanks in advance,
> Curtis
>
>
> Curtis
> https://curtis.maurand.com
>
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> https://mailman.powerdns.com/mailman/listinfo/pdns-users
--
Curtis
https://curtis.maurand.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20230310/26c0a00c/attachment.htm>
More information about the Pdns-users
mailing list