notify: and provide-xfr:

NSD
1

Hi,

I noticed that notify: does not seem to be enough to allow axfr's. I
had to explicitely also add provide-xfr:.

Is there any situation where one would want to send a notify to an
entity which is then not allowed to actually axfr?
In other words, why doesn't notify: imply provide-xfr: ?

I can see it the other way around, where you don't want to notify but
allow axfr, so having seperate options is still useful.

Paul

2

Off the top of my head

Sending notifies to a monitoring system
Sending notifies from secondaries to other secondaries but only doing axfr
from the master server

John

3

Sending notifies to a monitoring system

Okay (though there would be no harm and extra functionality allow the
monitoring system to also do an axfr and do content checks)

Sending notifies from secondaries to other secondaries but only doing axfr
from the master server

Wouldn't nsd attempt an axfr from whomever sends the notify, if it is an
allowed ip?

But I guess people can come up with scenario's, so there is a valid
point at keeping the functionality.

Paul

4

Paul Wouters wrote:

Wouldn't nsd attempt an axfr from whomever sends the notify, if it is an
allowed ip?

Yes, it does.

Best regards,
   Wouter