Re: failed multi-view zone transfer

On 22 Jan 2011, at 18:29, jeffreyp wrote: it's the transfers that are not happening. and, specifically, just the transfers of the internal view to the slave on the different subnet. You've mentioned that the slave receives and logs the NOTIFY. Do you see it (trying to) start

Re: failed multi-view zone transfer

Notifications by default do not go to the server listed in the mname field of the SOA record, so that the primary master does not notify itself. If you put the actual primary master's name in the mname, does it work correctly? You saud that also-notify lists the slaves. This should ensure that

Re: failed multi-view zone transfer

thanks chris. sorry if i've confused anyone. the notifications appear to be working fine. i enabled notify logging on the slaves and do see the notifications at the slaves, as expected. it's the transfers that are not happening. and, specifically, just the transfers of the internal view

failed multi-view zone transfer

greetings, i'm in the midst of an odd problem (to me, anyway) and would appreciate any pointers. three servers, all running bind-9.7.2-P3 compiled from source with the same options. one master; two slaves. two views: internal and external. one master and one slave are on the same subnet