slave to slave zone transfers HOWTO?

Joseph S D Yao jsdy at center.osis.gov
Fri Oct 11 20:15:44 UTC 2002


On Fri, Oct 11, 2002 at 01:20:58PM -0600, Cricket Liu wrote:
...
> Slaves send NOTIFYs to all authoritative name servers except the one
> in the MNAME field by default.  To really tune your NOTIFY setup,
> you could set the "superslave" to use "notify explicit" and send NOTIFY
> messages only to the "subslave."  Then you'd set "notify no" on all slaves
> that weren't themselves masters.

This suprises me.

Let's say you have three peer servers, A, B, and C.  Internally, A has
the "master" role, and appears in the MNAME field of the SOA.

Cricket changes the zone on A.  A sends out NOTIFYs to B and C.  B and
C respond by checking serial numbers and then requesting a zone
transfer from A.

So now, per what you have said, B and C each send NOTIFYs to each
other.  What do they do?  Check serial numbers with A a second time?

Say, instead of 3 servers, you have 30.  Yeah, yeah, don't quibble,
this is a Gnedenken experiment.  The 29 non-masters all send each other
NOTIFYs.  So each non-master receives 28 NOTIFYs after already updating
their zone files.

Can this really be correct?

> This is, by the way, in the cookbook.  ;-)

;-)

-- 
Joe Yao				jsdy at center.osis.gov - Joseph S. D. Yao
OSIS Center Systems Support					EMT-B
-----------------------------------------------------------------------
   This message is not an official statement of OSIS Center policies.


More information about the bind-users mailing list