On Nov 13 2008, Justin Shore wrote: >Res wrote: >> Is that the only difference or just main difference? IOW, why not just >> allow the "trusted" ACL members to do recursive, it'll shorten things a >> lot. > >Well, that's the most important difference to me. If you look at the >config from the email archives there are some other differences such as >additional-from-auth/cache, provide-ixfr, allow-transfer, and some zone >file differences.
I can't find the posting that you said contained your full confiig file, but are you using ixfr-from-differences on these zones whose master files are shared between views? Because this ... >Nov 12 23:39:39 maple1 named[12813]: reloading zones succeeded >Nov 12 23:39:39 maple1 named[12813]: zone zone.net/IN/trusted: loaded >serial 2008111206 >Nov 12 23:39:39 maple1 named[12813]: zone zone.net/IN/trusted: sending >notifies (serial 2008111206) >Nov 12 23:39:39 maple1 named[12813]: malformed transaction: >my/my-zones/zone.net.master.jnl last serial 2008111206 != transaction >Nov 12 23:39:39 maple1 named[12813]: client aaa.bbb.ccc.ddd#44588: view >trusted: transfer of 'zone.net/IN': AXFR started >Nov 12 23:39:39 maple1 named[12813]: client aaa.bbb.ccc.ddd#44588: view >trusted: transfer of 'zone.net/IN': AXFR ended ... is very suggestive that one view has written a journal file which the other one then considers corrupt. Or maybe both try to write it simultaneously... If so, try turning off ixfr-from-differecences in at least one view, and see if that makes yourzone reloading problem go away. Then, if you really need ixfr-from-differences in both views, use the "journal" setting in the "zone" statements so that the views use different journal files from each other, for such zones. -- Chris Thompson Email: [EMAIL PROTECTED]
