On 2016-05-18 22:50, David-2 wrote:
> This type of traffic is really common. You'll see all sorts of things
> trying to do AXFRs from you, DDNS updates, etc. You're probably only
> noticing it now because you've been looking into this issue/paying
> attention to it.
You are probably 100% right
Forgot to add this as reference when and how the slave is notified ...
- cut here -
DNS NOTIFY works like this: when a primary master name server notices that
the serial number of a zone has changed, it sends a special announcement to
all of the slave name servers for that zone. The prima
Hi.
I read your link about publishing real FQDNs an IPs, however I'm very
reluctant to this ... I explain ... I'm not the super pro (as you noticed
already) in this subject and I don't really know about the full range of
potential consequences. I see already now some AXFR attempts from IPs from
pa
Yes, 3.3.
But "prevent-self-notification=yes" still triggers self notifications.
Why were they implemented at a first place?
I don't see the usefullness.
--
View this message in context:
http://powerdns.13854.n7.nabble.com/why-self-notification-tp12287p12289.html
Sent from the PowerDNS mailing
Hi.
PowerDNS newbie question (sorry). syslog shows (anonymized):
May 15 19:51:46 gany pdns[30950]: 1 domain for which we are master needs
notifications
May 15 19:51:46 gany pdns[30950]: Queued notification of domain
'ddns.mydomain.com' to 185.3.195.46
May 15 19:51:46 gany pdns[30950]: Remote 185.