<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
Currently running Bind v9.11.4:<br>
<br>
Several years ago, I implemented multiple VIEWs using (almost) the
exact example in the Reference Manual. However, I wanted the <span
style="left: 286.182px; top: 537.805px; font-size: 14.944px;
font-family: monospace; transform: scaleX(0.996267);" dir="ltr">"example-internal.db"</span>
and <span style="left: 286.182px; top: 537.805px; font-size:
14.944px; font-family: monospace; transform: scaleX(0.996267);"
dir="ltr">"example-external.db"</span> to be the same file.<br>
<br>
This worked until I wanted to have <span style="left: 232.383px;
top: 501.275px; font-size: 14.944px; font-family: monospace;
transform: scaleX(0.996267);" dir="ltr">"example.com"</span>
updateable via ddns. I don't remember the exact error, but I have a
note in my configuration file of <i>"don't do that!"</i> (use the
same file). So, I removed the first zone declaration for <span
style="left: 232.383px; top: 501.275px; font-size: 14.944px;
font-family: monospace; transform: scaleX(0.996267);" dir="ltr">"example.com"</span>.
That was still with Bind v9, but a lesser minor version.<br>
<br>
So, the result is that I can't do a <font face="monospace">"dig -k
tsig.file @localhost -t axfr example.com"</font> from the server
command line. The transfer is denied, because "match-clients"
forces me into the first (internal) VIEW.<br>
<br>
The server is behind a firewall (which has a forward to the server),
so "dig" works if I specify <font face="monospace">"dig -k
tsig.file @ns1.example.com"</font>. Because of this, I can still
use "dig" like I want on the server.<br>
<br>
However, I'd think this must be a common issue. Any resolution
(like recognizing & dealing with two references to a dynamically
updated file)?<br>
</body>
</html>