Thanks for the encouragement folks, I forged ahead and I've got a different error now:
"response-policy zone 'rpz1.m3047.net' for view standard is not a master or slave zone" That's the final denoument. There are several intermediate steps, such as moving all zone definitions into the views and converting all zone references in the second view to "in-view standard;" (where "standard" is the name of the first view). * There are a total of three RPZs. * Two are utilized in the first view. (actually this is a lie) * All three are utilized in the second view. and the "lie" is that the "unused" RPZ is dynamically updated in the first view (that's where update requests are sent); I suppose I could jigger that so that the updates happen in the second view. But the stopper is that error message, and that RPZ is common to both views. This is 9.12 FWIW. -- Fred Morris
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users