<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Thanks for the encouragement folks, I forged ahead and I've got a
different error now:</p>
<blockquote>
<p>"response-policy zone 'rpz1.m3047.net' for view standard is not
a master or slave zone"</p>
</blockquote>
<p>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).<br>
</p>
<ul>
<li>There are a total of three RPZs.</li>
<li>Two are utilized in the first view. (actually this is a lie)</li>
<li>All three are utilized in the second view.</li>
</ul>
<p>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.</p>
<p>This is 9.12 FWIW.</p>
<p>--</p>
<p>Fred Morris</p>
<p><br>
</p>
</body>
</html>