<div style="font-family: Arial, sans-serif; font-size: 14px;">Hi Peter,</div><div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div><div style="font-family: Arial, sans-serif; font-size: 14px;">Thank you, your suggestion pointed me in the correct direction.  I'm now using the "in-view" zone option to share zones between views.  Kea is now sending ddns updates to the primary view which are visible to all other views now.  This also simplified the bind9 configuration.</div><div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div><div style="font-family: Arial, sans-serif; font-size: 14px;">Thanks again,</div><div style="font-family: Arial, sans-serif; font-size: 14px;"><br></div><div style="font-family: Arial, sans-serif; font-size: 14px;">Ben</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;" class="protonmail_signature_block protonmail_signature_block-empty">
    <div class="protonmail_signature_block-user protonmail_signature_block-empty">
        
            </div>
    
            <div class="protonmail_signature_block-proton protonmail_signature_block-empty">
        
            </div>
</div>
<div style="font-family: Arial, sans-serif; font-size: 14px;"><br><div class="protonmail_quote">
        On Tuesday, November 25th, 2025 at 11:26 AM, Peter Davies <peterd@isc.org> wrote:<br>
        <blockquote class="protonmail_quote" type="cite">
            
    <p><font face="monospace">Hi Ben,<br>
           In a kea-dhcp-ddns configuration file, each “dns-domain”
        definition can include <br>
        a single "key-name" statement, which refers to a previously
        defined TSig key.<br>
        <br>
        Since kea-dhcp-ddns does not permit duplicate dns-domain
        definitions, assigning <br>
        multiple keys to the same domain is not possible.<br>
        <br>
        One option to overcome this is to load the same zone in all
        views on your DNS <br>
        server. This could address the key limitation of the assignment.<br>
        <br>
        <br>
        If multiple forward zones were updated at each lease renewal,
        implementing <br>
        conflict resolution would be rather complex.<br>
        <br>
        Kind Regards Peter</font></p>
    <div class="moz-cite-prefix">On 24/11/2025 16.30, Ben Sparks
      (bzsparks.com) via Kea-users wrote:<br>
    </div>
    <blockquote type="cite">
      
      <div style="font-family: Arial, sans-serif; font-size: 14px;">
        <div><span>Hello,</span>
          <div><br>
          </div>
          <div><span>I have a question about kea ddns sending to bind9
              with multiple views for the same zone.  We separate
              different networks by view for control of response policy
              zones but I would like all users to be able to perform
              forward and reserve resolutions for devices.</span></div>
          <div><span><br>
            </span></div>
          <div><span><span>Is something like this possible?</span><br>
            </span></div>
          <div><br>
          </div>
          <div>#bind9 views</div>
          <div><span>view 1</span></div>
          <div><span>tsig1-key</span></div>
          <div><span>zone <a target="_blank" rel="noreferrer nofollow noopener" href="http://iot.example.com">iot.example.com</a></span></div>
          <div><br>
          </div>
          <div><span>view 2 </span></div>
          <div><span>tsig2-key</span></div>
          <div><span>zone <a target="_blank" rel="noreferrer nofollow noopener" href="http://iot.example.com">iot.example.com</a></span></div>
          <div><br>
          </div>
          <div><span>view 3</span></div>
          <div><span>tsig3-key</span></div>
          <div><span>zone <a target="_blank" rel="noreferrer nofollow noopener" href="http://iot.example.com">iot.example.com</a></span></div>
          <div><br>
          </div>
          <div><span>#kea ddns</span></div>
          <div><span>"ddns-domains": [</span></div>
          <div><span>    {</span></div>
          <div><span>        "name": "<a target="_blank" rel="noreferrer nofollow noopener" href="http://iot.example.com">iot.example.com</a>.",</span></div>
          <div><span>        "key-names": [</span></div>
          <div><span>            "tsig1-key",</span></div>
          <div><span>            "tsig2-key",</span></div>
          <div><span>            "tsig3-key"</span></div>
          <div><span>        ],</span></div>
          <div><span>        "dns-servers": [</span></div>
          <div><span>            { "ip-address": "10.1.1.1" }</span></div>
          <div><span>        ]</span></div>
          <div><span>    }</span></div>
          <div><span>]</span></div>
          <div><br>
          </div>
          <div><span>"ddns-domains": [</span></div>
          <div><span>    {</span></div>
          <div><span>        "name": "1.2.10.in-addr.arpa.",</span></div>
          <div><span>        "key-names": [</span></div>
          <div><span>            "tsig1-key",</span></div>
          <div><span>            "tsig2-key",</span></div>
          <div><span>            "tsig3-key"</span></div>
          <div><span>        ],</span></div>
          <div><span>        "dns-servers": [</span></div>
          <div><span>            { "ip-address": "10.1.1.1" }</span></div>
          <div><span>        ]</span></div>
          <div><span>    }</span></div>
          <span>]</span></div>
        <div><span><br>
          </span></div>
        <div><span>Thank you,</span></div>
        <div><span><br>
          </span></div>
        <span><span>Ben</span></span><br>
      </div>
      <div style="font-family: Arial, sans-serif; font-size: 14px;" class="protonmail_signature_block protonmail_signature_block-empty">
        <div class="protonmail_signature_block-user protonmail_signature_block-empty">
        </div>
        <div class="protonmail_signature_block-proton protonmail_signature_block-empty">
        </div>
      </div>
      <br>
      <fieldset class="moz-mime-attachment-header"></fieldset>
    </blockquote>
    <pre class="moz-signature" cols="72">--
Peter Davies
Support Engineer
Internet Systems Corporation
</pre>
  


        </blockquote><br>
    </div></div>