<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Courier New";}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div class=WordSection1><p class=MsoNormal>Thanks so much for both replies. I made the changes you mentioned. I found I also had to change the ip-addess to the ip address of the server. When I had it as 127.0.0.1, I was getting a corrupt reply error from the DNS Server in the logs. Thankfully now, the server is updating. I have just one last error now that I am trying to figure out. This is in the kea-dhcp-ddns.conf file. I keep getting the error :</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><b>INFO/keactrl: Starting /usr/local/sbin/kea-dhcp-ddns -c /usr/local/etc/kea/kea-dhcp-ddns.conf<o:p></o:p></b></p><p class=MsoNormal><b>2020-06-09 23:13:15.700 FATAL [kea-dhcp-ddns.dctl/72504] DCTL_CONFIG_FILE_LOAD_FAIL DhcpDdns reason: Configuration parsing failed: /usr/local/etc/kea/kea-dhcp-ddns.conf:28.3-11: syntax error, unexpected loggers, expecting "," or }<o:p></o:p></b></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I get this when I enable the logging section in the file. I am not sure why. I pretty much used the defaults from the sample file. I even compared my file with the sample file and everything there is the same except that I enabled debugging in mine. </p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Please note my entire kea-dhcp-ddns.conf below. I have been going through but I can’t seem to find a syntax error.</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>{</p><p class=MsoNormal>{</p><p class=MsoNormal>"DhcpDdns": {</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> "tsig-keys": [</p><p class=MsoNormal> {</p><p class=MsoNormal> "name": "homelocal.key",</p><p class=MsoNormal> "algorithm": "HMAC-SHA256",</p><p class=MsoNormal> "secret": "jo/1eHCej8eFTY2aqvICCNINVvbbv9KuEU="</p><p class=MsoNormal> }</p><p class=MsoNormal> ],</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> "forward-ddns": {</p><p class=MsoNormal> "ddns-domains": [</p><p class=MsoNormal> {</p><p class=MsoNormal> "name": "home.local.",</p><p class=MsoNormal> "key-name": "homelocal.key",</p><p class=MsoNormal> "dns-servers": [</p><p class=MsoNormal> {</p><p class=MsoNormal> "hostname": "",</p><p class=MsoNormal> "ip-address": "192.168.40.10",</p><p class=MsoNormal> "port": 53</p><p class=MsoNormal> }</p><p class=MsoNormal> ]</p><p class=MsoNormal> }</p><p class=MsoNormal> ]</p><p class=MsoNormal> }</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> "loggers": [</p><p class=MsoNormal> {</p><p class=MsoNormal> "name": "kea-dhcp-ddns",</p><p class=MsoNormal> "output_options": [</p><p class=MsoNormal> {</p><p class=MsoNormal> "output": "/var/log/kea-ddns.log"</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal> }</p><p class=MsoNormal> ],</p><p class=MsoNormal> "severity": "DEBUG",</p><p class=MsoNormal> // If DEBUG level is specified, this value is used. 0 is least verbose,</p><p class=MsoNormal> // 99 is most verbose. Be cautious, Kea can generate lots and lots</p><p class=MsoNormal> // of logs if told to do so.</p><p class=MsoNormal> "debuglevel": 99</p><p class=MsoNormal> }</p><p class=MsoNormal> ]</p><p class=MsoNormal>}</p><p class=MsoNormal>}</p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">Mail</a> for Windows 10</p><p class=MsoNormal><o:p> </o:p></p><div style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a href="mailto:jschaeffer@harmonywave.com">Joshua Schaeffer</a><br><b>Sent: </b>Tuesday, June 9, 2020 1:06 PM<br><b>To: </b><a href="mailto:kea-users@lists.isc.org">kea-users@lists.isc.org</a><br><b>Subject: </b>Re: [Kea-users] DDNS Error</p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On 6/9/20 11:28 AM, Stephen Morris wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal>2. In the "forward-ddns" section of the kea-dhcp-ddns.conf configuration <o:p></o:p></p><pre>file, "key-name" is set to blank, so no key is being used to communicate</pre><pre>with the BIND server. However, in the BIND configuration, the</pre><pre>"allow-update" clause means that BIND requires a key in order to update</pre><pre>the "home.local" zone.</pre><pre><o:p> </o:p></pre><pre>3. The name of the only defined key in the kea-dhcp-ddns configuration</pre><pre>is "homelocal.key." (i.e. with a trailing period), but the name of the</pre><pre>key in BIND is "homelocal.key" (without the trailing period). Assuming</pre><pre>the defined key is the one that should be used to communicate with BIND,</pre><pre>the names should match.</pre></blockquote><p class=MsoNormal>I'd agree with Stephen that you need to make sure your key-name is specified in the forward-ddns section and that it matches the key name that BIND is configured to use. In addition to this you are getting an RCODE response, which means that you are getting an error from the DNS server. As you have DNS logs set to debug you should look through those logs to see if the DNS server will give you more information about the specifics of the error.<br><br><o:p></o:p></p><pre>-- </pre><pre>Thanks,</pre><pre>Joshua Schaeffer</pre><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'><o:p> </o:p></span></p></div></body></html>