<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 19/04/2025 02:06, Marek Kozlowski
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:e42348a7-4310-4cf8-a675-bca378bd44cf@mini.pw.edu.pl">view
pub {
<br>
match-clients { any; };
<br>
</blockquote>
<p>Hi Marek.</p>
<p>What you have created looks great, and looks like it will work
fine. I have one minor suggestion though: For consistency with
your other views, and to eliminate the possibility of accidentally
transferring the public zone to a private view <i>as a
side-effect of any future configuration changes</i>, I'd change
the above match-clients line to:</p>
<pre>match-clients { !key priv1; !key priv2; key pub; any; };
</pre>
<p>This tweak will prevent the public view from being accessed with
either of the private keys. And while that isn't going to happen
with your current configuration (due to the order of the views and
the match-clients stanzas in those views), if in the future you
change something - such as adding a match-destinations stanza to
one of the other views - then there is a risk that your secondary
server could inadvertently end up transferring the zone from the
public view in spite of having signed the zone transfer request
with one of the private keys.<br>
</p>
<p>Nick.<br>
</p>
</body>
</html>