DDNS not connecting to noip

[MajorBob]

I'm having an issue with my ddns connection to NoIp where opnsense is not grabbing the IP Address and talking to noip.

My settings are:
Service: noip
Username
Password
Hostnames (my actual hostname and the one they say to use)
Check IP method: Interface
Interface to Monitor: WAN
Timeout: 10
Force SSL: checked

I've tried it with both hostnames individually, check IP as noipv4, Force SSL unchecked and with the backend in both native and ddclient.

I have just upgraded to the latest version (25.7.2) and this issue was present before the update (from 25.7.0).

When I log in to noip account I see the last update was on the 18th August.

In the logs in opnsense I get "no global IP address detected, check config if warning persists"

In the table showing ddns configs it is not updating with an IP address and time, and on the lobby widget it is also no updating.

Can anyone point out where I'm going wrong?

[Netlearn]

Mine is working flawless at this time.

The only difference is that I only have my hostname in the list.

I do have the same line in logs but it's some minutes before the update. No logs about correct updates.

[MajorBob]

I've just restarted the system with only my hostname set and still no connection.

Attached picture is the logs since boot.  Everything else is working, but this is stopping my NAS and VPN from working.

Noip is still saying the 18th for the last update.

[MajorBob]

I think I've found a potential cause.  My config file doesn't contain the ddns config.

Code Select Expand

syslog=yes
pid=/var/run/ddclient.pid
verbose=yes
That's it.  No actual ddns config in there at all.

[MajorBob]

Solved the problem.

Settings for NoIp I have to use are:

Code Select Expand

Enabled: checked
Description: ****
Service: Custom
Protocol: DynDNS 2
Server: dynupdate.no-ip.com
Username: ***
Password: ***
Wildcard: unchecked
Hostname(s): ****
Check ip method: Interface
Interface to monitor: WAN
Check ip timeout: 10
Force SSL: checked

[Netlearn]

There is a "General Settings" tab next to "Accounts". By default, the "native" backend is selected, so no ddclient config.

Creating a "Custom" account profile can be a workaround but it doesn't explain why the no-ip profile fails in your case.

Sadly, lack of logs for this service makes tracking issues hard.