<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 10/10/16 1:23 PM, Richard Holbo
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAJV392N15WFwVHCAU_7xSNg31keYXvnZxvWFju=agcgaDQWy-w@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>
          <div>
            <div>
              <div>
                <div>
                  <div>Am doing my first deployment of KEA after using
                    ISC-DHCP for..ever.<br>
                    <br>
                  </div>
                  Am trying to replicate an existing configuration with
                  multiple subnets updating different forward DNS
                  domains and am unclear on how to accomplish this as
                  all examples/docs I've found only seem to use a single
                  forward domain.<br>
                  <br>
                </div>
                I've got both forward and reverse working, forward for a
                single domain, and reverse for whatever the subnet is. 
                My issue seems to be the following commands:<br>
                <br>
                <span class="gmail-gI"></span>{<br>
                <br>
                  "dhcp-ddns": { "enable-updates": true,<br>
                    "qualifying-suffix": "<a moz-do-not-send="true"
                  href="http://bogus.net">bogus.net</a>",<br>
                    "override-client-update": true<br>
                },<br>
                <br>
              </div>
              These seem to be required in the DHCP4 config but then
              seem to override any settings in the ddns config<br>
              <br>
                "forward-ddns" : {<br>
                  "ddns-domains": [<br>
                      {<br>
                      "name": "<a moz-do-not-send="true"
                href="http://bogus.net">bogus.net</a>.",<br>
                      "dns-servers": [ { "ip-address": "re.dac.ted",
              "port": 53 } ]<br>
                      },<br>
                      {<br>
                      "name": "wireless.bogus.",<br>
                      "dns-servers": [ { "ip-address": "re.dac.ted",
              "port": 53 } ]<br>
                      },<br>
                      {<br>
                       "name": "bogus.",<br>
                       "dns-servers": [ { "ip-address": "re.dac.ted",
              "port": 53 } ]<br>
                        },<br>
                      ]<br>
                  },<br>
              <br>
            </div>
            <div>The following is info is set under the "subnet" section
              for each:<br>
              -----<br>
                      {<br>
                          "name": "domain-name",<br>
                          "data": "<a moz-do-not-send="true"
                href="http://bogus.net">bogus.net</a>"<br>
                      },<br>
            </div>
            <div>-----<br>
                      {<br>
                          "name": "domain-name",<br>
                          "data": "bogus.wireless"<br>
                      },<br>
              -----<br>
                      {<br>
                          "name": "domain-name",<br>
                          "data": "bogus"<br>
                      },<br>
              <br>
            </div>
            I'm sure it's something simple I'm missing but been banging
            my head against it for a couple of days.  All forward DNS
            goes to <a moz-do-not-send="true" href="http://bogus.net">bogus.net</a>
            irrespective of the domain-name settings of the subnet.<br>
            <br>
          </div>
          /thanks<br>
        </div>
        /rh<br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Kea-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Kea-users@lists.isc.org">Kea-users@lists.isc.org</a>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/kea-users">https://lists.isc.org/mailman/listinfo/kea-users</a>
</pre>
    </blockquote>
    <p><tt>Hello Richard:</tt></p>
    <p><tt><br>
        If I understand correctly, you're thinking that kea-dhcp4 will
        use the "domain-name" option to qualify the hostname sent by
        your clients as the FQDN for the DNS entries.  While this is a
        very useful feature, Kea does not yet support it.  Currently,
        the dhcp server can only be configured with a single, global
        qualifying-suffix.  It should be possible to override this
        behavior by writing a custom hook for the lease4_select hook
        point.  This hook point is called after the subnet has been
        selected and a lease has been determined but before the DDNS
        request(s) are created. The hook would need to create an FQDN
        option using the domain-name value from the selected subnet and
        add the option to the inbound packet, the "query" argument in
        the lease4_select.  The server will see this FQDN option and use
        it when forming the DDNS requests sent to kea-dhcp-ddns (aka
        D2).<br>
      </tt></p>
    <p><tt>Writing hooks is discussed in detail with examples in our
        developer's guide:</tt></p>
    <p><tt><a class="moz-txt-link-freetext" href="https://jenkins.isc.org/job/Fedora20_32_doxygen_doc/doxygen/de/df3/dhcpv4Hooks.html">https://jenkins.isc.org/job/Fedora20_32_doxygen_doc/doxygen/de/df3/dhcpv4Hooks.html</a></tt></p>
    <p><tt>In the meantime, I have opened a ticket in our Trac, to
        request the behavior:</tt></p>
    <p><tt><a class="moz-txt-link-freetext" href="http://kea.isc.org/ticket/5048#ticket">http://kea.isc.org/ticket/5048#ticket</a></tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt>Sincerely,</tt></p>
    <p><tt>Thomas Markwalder</tt></p>
    <p><tt>ISC Software Engineering<br>
      </tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt> <br>
      </tt></p>
    <p><tt><br>
      </tt></p>
    <p><tt><br>
      </tt></p>
  </body>
</html>