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
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 nsd-users-bounces at NLnetLabs.nl wrote on 17/09/2007 03:01:50:> > 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 > _______________________________________________ > nsd-users mailing list > nsd-users at NLnetLabs.nl > http://open.nlnetlabs.nl/mailman/listinfo/nsd-users