<div dir="ltr">Hi Joshua,<div><br></div><div>Thank you for the response.</div><div>I may be wrong, but I would expect that listening on 127.0.0.1 should work as it is the server itself.</div><div>In fact, the documentation includes a warning for any other configuration:</div><div><a href="https://kea.readthedocs.io/en/kea-1.6.1/arm/ddns.html#global-server-parameters">https://kea.readthedocs.io/en/kea-1.6.1/arm/ddns.html#global-server-parameters</a></div><div>In any case, I changed it to the static Docker network IP 172.16.100.4 and restarted it.</div><div>I note that upon startup now the following warning appears:</div><div>2020-04-30 07:35:29.317 INFO [kea-dhcp-ddns.dctl/1] DCTL_CONFIG_COMPLETE server has completed configuration: listening on 172.16.100.4, port 53001, using UDP<br></div><div>2020-04-30 07:35:29.319 WARN [kea-dhcp-ddns.dhcpddns/1] DHCP_DDNS_NOT_ON_LOOPBACK the DHCP-DDNS server has been configured to listen on 172.16.100.4 which is not the local loopback. This is an insecure configuration supported for testing purposes only<br></div><div><br></div><div>Following your suggesting I installed ss (iproute2). Oddly enough, it does not seem to be listening to any ports.</div><div>root@
a987aac4aa8b:/# ss<br>Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port<br></div><div><br></div><div>One may wonder if kea-dhcp-ddns is really running.</div><div>I don't have ps available in the container, but if I try to run it again manually I naturally get the following:</div><div>root@a987aac4aa8b:/# /usr/sbin/kea-dhcp-ddns -c /etc/kea/kea-dhcp-ddns.conf<br></div><div>2020-04-30 07:34:00.521 FATAL [kea-dhcp-ddns.dctl/14] DCTL_ALREADY_RUNNING kea-dhcp-ddns already running? Daemon::createPIDFile: PID: 1 exists, PID file: /var/run/kea/kea-dhcp-ddns.kea-dhcp-ddns.pid<br>Service failed: Launch Failed: Daemon::createPIDFile: PID: 1 exists, PID file: /var/run/kea/kea-dhcp-ddns.kea-dhcp-ddns.pid<br>root@a987aac4aa8b:/#<br></div><div><br></div><div>Any idea why it is not listening for connections?</div><div>For reference, here are the debug logs:</div><div>2020-04-30 07:35:29.313 DEBUG [kea-dhcp-ddns.dhcpddns/1] DHCP_DDNS_CONFIGURE configuration update received: { "control-socket": { "socket-name": "/tmp/kea-dhcp-ddns-ctrl.sock", "socket-type": "unix" }, "forward-ddns": { "ddns-domains": [ { "dns-servers": [ { "ip-address": "172.16.100.1" }, { "ip-address": "172.16.100.2" } ], "key-name": "rndc-key", "name": "dono.local." } ] }, "ip-address": "172.16.100.4", "loggers": [ { "debuglevel": 99, "name": "kea-dhcp-ddns", "output_options": [ { "flush": true, "maxsize": 1048576, "maxver": 3, "output": "/etc/kea/kea-ddns.log" } ], "severity": "DEBUG" } ], "port": 53001, "reverse-ddns": { "ddns-domains": [ { "dns-servers": [ { "ip-address": "172.16.100.1" }, { "ip-address": "172.16.100.2" } ], "key-name": "rndc-key", "name": "10.10.10.in-addr.arpa." }, { "dns-servers": [ { "ip-address": "172.16.100.1" }, { "ip-address": "172.16.100.2" } ], "key-name": "rndc-key", "name": "20.10.10.in-addr.arpa." }, { "dns-servers": [ { "ip-address": "172.16.100.1" }, { "ip-address": "172.16.100.2" } ], "key-name": "rndc-key", "name": "40.10.10.in-addr.arpa." } ] }, "tsig-keys": [ { "algorithm": "hmac-sha256", "name": "rndc-key", "secret": "<secret>" } ] }<br>2020-04-30 07:35:29.313 DEBUG [kea-dhcp-ddns.dctl/1] DCTL_CONFIG_START parsing new configuration: { "control-socket": { "socket-name": "/tmp/kea-dhcp-ddns-ctrl.sock", "socket-type": "unix" }, "forward-ddns": { "ddns-domains": [ { "dns-servers": [ { "ip-address": "172.16.100.1" }, { "ip-address": "172.16.100.2" } ], "key-name": "rndc-key", "name": "dono.local." } ] }, "ip-address": "172.16.100.4", "loggers": [ { "debuglevel": 99, "name": "kea-dhcp-ddns", "output_options": [ { "flush": true, "maxsize": 1048576, "maxver": 3, "output": "/etc/kea/kea-ddns.log" } ], "severity": "DEBUG" } ], "port": 53001, "reverse-ddns": { "ddns-domains": [ { "dns-servers": [ { "ip-address": "172.16.100.1" }, { "ip-address": "172.16.100.2" } ], "key-name": "rndc-key", "name": "10.10.10.in-addr.arpa." }, { "dns-servers": [ { "ip-address": "172.16.100.1" }, { "ip-address": "172.16.100.2" } ], "key-name": "rndc-key", "name": "20.10.10.in-addr.arpa." }, { "dns-servers": [ { "ip-address": "172.16.100.1" }, { "ip-address": "172.16.100.2" } ], "key-name": "rndc-key", "name": "40.10.10.in-addr.arpa." } ] }, "tsig-keys": [ { "algorithm": "hmac-sha256", "name": "rndc-key", "secret": "<secret>" } ] }<br>2020-04-30 07:35:29.315 INFO [kea-dhcp-ddns.commands/1] COMMAND_ACCEPTOR_START Starting to accept connections via unix domain socket bound to /tmp/kea-dhcp-ddns-ctrl.sock<br>2020-04-30 07:35:29.317 INFO [kea-dhcp-ddns.dctl/1] DCTL_CONFIG_COMPLETE server has completed configuration: listening on 172.16.100.4, port 53001, using UDP<br>2020-04-30 07:35:29.317 DEBUG [kea-dhcp-ddns.dctl/1] DCTL_RUN_PROCESS DhcpDdns starting application event loop<br>2020-04-30 07:35:29.318 INFO [kea-dhcp-ddns.dhcpddns/1] DHCP_DDNS_STARTED Kea DHCP-DDNS server version 1.6.2 started<br>2020-04-30 07:35:29.318 DEBUG [kea-dhcp-ddns.commands/1] COMMAND_REGISTERED Command build-report registered<br>2020-04-30 07:35:29.318 DEBUG [kea-dhcp-ddns.commands/1] COMMAND_REGISTERED Command config-get registered<br>2020-04-30 07:35:29.318 DEBUG [kea-dhcp-ddns.commands/1] COMMAND_REGISTERED Command config-reload registered<br>2020-04-30 07:35:29.318 DEBUG [kea-dhcp-ddns.commands/1] COMMAND_REGISTERED Command config-set registered<br>2020-04-30 07:35:29.318 DEBUG [kea-dhcp-ddns.commands/1] COMMAND_REGISTERED Command config-test registered<br>2020-04-30 07:35:29.318 DEBUG [kea-dhcp-ddns.commands/1] COMMAND_REGISTERED Command config-write registered<br>2020-04-30 07:35:29.318 DEBUG [kea-dhcp-ddns.commands/1] COMMAND_REGISTERED Command shutdown registered<br>2020-04-30 07:35:29.318 DEBUG [kea-dhcp-ddns.commands/1] COMMAND_REGISTERED Command version-get registered<br>2020-04-30 07:35:29.318 DEBUG [kea-dhcp-ddns.dhcpddns/1] DHCP_DDNS_QUEUE_MGR_RECONFIGURING application is reconfiguring the queue manager<br>2020-04-30 07:35:29.319 WARN [kea-dhcp-ddns.dhcpddns/1] DHCP_DDNS_NOT_ON_LOOPBACK the DHCP-DDNS server has been configured to listen on 172.16.100.4 which is not the local loopback. This is an insecure configuration supported for testing purposes only<br>2020-04-30 07:35:29.319 DEBUG [kea-dhcp-ddns.dhcpddns/1] DHCP_DDNS_QUEUE_MGR_STARTED application's queue manager has begun listening for requests.<br></div><div><br></div><div>And here are interface details from within the container:</div><div>root@a987aac4aa8b:/# ip addr<br>1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000<br> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00<br> inet <a href="http://127.0.0.1/8">127.0.0.1/8</a> scope host lo<br> valid_lft forever preferred_lft forever<br>287: eth0@if288: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default<br> link/ether 02:42:ac:10:64:04 brd ff:ff:ff:ff:ff:ff link-netnsid 0<br> inet <a href="http://172.16.100.4/24">172.16.100.4/24</a> brd 172.16.100.255 scope global eth0<br> valid_lft forever preferred_lft forever<br></div><div><br></div><div>Regards,</div><div>Ben Monroe</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 30, 2020 at 2:30 PM Joshua Schaeffer <<a href="mailto:jschaeffer@harmonywave.com">jschaeffer@harmonywave.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
You are sending to 172.16.100.4 from the DHCP4 server, but listening
on localhost on the DDNS server:<br>
<br>
On 4/29/20 9:45 PM, Ben Monroe wrote:<br>
<blockquote type="cite">
<div dir="ltr"> "dhcp-ddns": {<br>
<div> "enable-updates": true,<br>
"qualifying-suffix": "dono.local.",<br>
"server-ip": "172.16.100.4"<br>
</div>
</div>
</blockquote>
<blockquote type="cite">
<div dir="ltr">
<div><br>
And in kea-dhcp-ddns.conf I have:<br>
{<br>
"DhcpDdns":<br>
{<br>
"ip-address": "127.0.0.1",<br>
"port": 53001, <br>
</div>
</div>
</blockquote>
You need to listen on your global IP address. Use <font face="Courier New">ss</font> or <font face="Courier New">netstat</font>
(if you have them available in your container) to confirm which
interface D2 is actually listening on.<br>
<pre cols="0">--
Thanks,
Joshua Schaeffer</pre>
</div>
</blockquote></div>