<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 08/10/2025 09:14, Darren Ankney
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAKabWHikaYUVH4u2G5B5HYH1WZ8MV-fER0B8XPt2uoftTZHghw@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">You could setup example.org and my.example.org as type "mirror"
(<a class="moz-txt-link-freetext"
href="https://bind9.readthedocs.io/en/v9.18.36/reference.html#namedconf-statement-type%20mirror"
moz-do-not-send="true">https://bind9.readthedocs.io/en/v9.18.36/reference.html#namedconf-statement-type%20mirror</a>)
if you are able to allow a zone transfer to your recursive nameserver
from 1.1.1.1 and 2.2.2.2. If you can't, then perhaps type "stub"
could work: <a class="moz-txt-link-freetext"
href="https://bind9.readthedocs.io/en/v9.18.36/reference.html#namedconf-statement-type%20stub"
moz-do-not-send="true">https://bind9.readthedocs.io/en/v9.18.36/reference.html#namedconf-statement-type%20stub</a></pre>
</blockquote>
<p>Please be aware of the following for mirror zones (from the first
link above):</p>
<blockquote>
<p><i>Use of this zone type with any zone other than the root
should be
considered experimental and may cause performance issues,
especially for zones that are large and/or frequently updated.</i></p>
</blockquote>
<p>(Perhaps a secondary zone would be a safer option than a mirror
zone?)</p>
<p>But I also agree that a stub or static-stub zone is a good option
to solve your problem.</p>
<p>Nick.</p>
</body>
</html>