Even with the latest update, duckdns doesn't work

[WhiteTiger]

Yesterday there was an update to the ddclient plugin.
Nonetheless, I still don't see duckdns working.

The backend is "ddclient", but even with "native" it doesn't work.
The account settings are:
Service = duckdns
Username = blank
Password = <token>
Hostnames = <hostname>.duckdns.org
Check ip method = Interface [IPv4]
Interface to monitor = WAN
Check ip timeout = 10
Force SSL = unchecked

The date reported in "Updated" is ten days ago and the IP is that of the opnsense WAN address (192.168.x.y), not the public address from the ISP.
Also in the duckdns.org panel the domain corresponds to this private IP and not the public one of the ISP.

I tried deleting the old configuration and recreating a new one even with a different description, but I still have the date of the last update 10 days ago and the WAN IP.

Obviously, if I type "ping hostname.duckdns.org" from my Win11 terminal I get the error "The host hostname.duckdns.org could not be found. Check that the name is correct and try again."

[Monviech (Cedrik)]

Maybe as an alternative, you could try out duckdns in the plugin in my signature. It has dynamic dns for this provider built in.

It's based on this extension here: https://github.com/mholt/caddy-dynamicdns

The plugin is pretty new but it's already tested and other people use it too, here's somebody who tried it out with desec as provider for dynamic dns and it works for them: https://github.com/Monviech/os-caddy-plugin/issues/77

[WhiteTiger]

Thanks for your reply.
However, your plugin appears to be a Reverse Proxy.
Since HA-Proxy is expected to be mounted, I don't want to create conflicts.

[Monviech (Cedrik)]

Yup that won't work together. Just wanted to offer it if you wanne try something new someday. ^^