Notify / Transfer Delays

Unlisted unlisted at gmail.com
Fri May 13 05:40:47 UTC 2005


> RFC 1996 suggests that it should be on the master

The problem we are having is AFTER the NOTIFY is sent, not before its
sent.  The slave delays 15 seconds before performing a zone transfer
from the master...

> I don't think notify has ever been intended to be an instant
replication

I agree on this one, however in previous versions it was instant
replication.  Just wondering what changed and if there is any control
over it.

RFC 1996 states that the slaves should queue upon receiving multiple
notifies but this is happening even with a single notify.  I assume
there is nothing wrong with delaying it, again, I'm just wondering if
its controllable or was changed from 9.2 to 9.3 for a reason.

"   4.4. A slave which receives a valid NOTIFY should defer action on
any
   subsequent NOTIFY with the same <QNAME,QCLASS,QTYPE> until it has
   completed the transaction begun by the first NOTIFY.  This duplicate
   rejection is necessary to avoid having multiple notifications lead
to
   pummeling the master server."

Thx,
Sam



More information about the bind-users mailing list