how to verify that ddclient (new DDNS) is working - FIXED

[axel2078]

How can I verify that ddclient is working properly and actually updating? I use No-IP for my DDNS service.  I set up ddclient tonight and for "Check IP method" I chose noip-ipv4 (not sure if this is the right option) and set it to listen on WAN.  Anyway, I checked the Dynamic DNS Log file and the only events that pop up are Notices and so far, this is all I'm seeing:

2022-05-17T18:42:04-05:00   Notice   ddclient[17457]   22328 - [meta sequenceId="1"] WARNING: found neither ipv4 nor ipv6 address   
2022-05-17T18:39:34-05:00   Notice   ddclient[17457]   99807 - [meta sequenceId="1"] WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner (fixed).   
2022-05-17T14:37:40-05:00   Notice   ddclient[12506]   69965 - [meta sequenceId="1"] WARNING: file /usr/local/etc/ddclient.conf: file /usr/local/etc/ddclient.conf must be accessible only by its owner (fixed).

It doesn't look like it's working to me.

[allebone]

No IP has a control panel you can log into also doesnt it?

[axel2078]

It does.  It shows that the last update occurred on May 13th.  The legacy DDNS client is still running on my OPNsense system, which is probably why it's still working.  I'm a bit hesitant about having to switch over to the ddclient because there doesn't seem to be much documentation on it and I'm afraid I won't be able to connect to my WireGuard VPN server since my external IP is dynamic.

[axel2078]

Update: I got it working by manually editing the ddclient.conf file using the below configuration:

Code: [Select]

use=web
web=checkip.dyndns.com
web-skip='Current IP Address: '

protocol=dyndns2
server=dynupdate.no-ip.com
login=myusername
password='mypass'
myhost.noip.me
It is now updating just fine.  Here's where I found the fix: https://unix.stackexchange.com/questions/218841/configure-debian-ddclient-with-dyndns-noip-com

[allebone]

I did it via the gui by selecting:

Enabled - Y
Service - Custom
Protocol - DynDns2
Server - dynupdate.no-ip.com
Username - <as appropriate>
Password - <as appropriate>
Wildcard - N
Hostnames - <as appropriate>
Check IP Method - Interface
Force SSL - Y
Interface to monitor - WAN

Then it worked fine.

[chemlud]

May I ask: What is the status of the new DDNS plugin? Is there a GUI-integration yet? Which DynDNS services are supported yet?

[lilsense]

you may want to check this thread: https://forum.opnsense.org/index.php?topic=26446.0;topicseen

[chemlud]

...16 pages of despair. But what is the status of this project, which is going to be online with 22.7? Is it the plan to make users with DynDNS switch to other FW software? I don't get the strong impetus driving this switch in DDNS plugin....

[lilsense]

if you plan on switching your FW just because of ddns, I highly recommend you move on to another FW. ROFL

I have a little rPI that does this without an issue, or an app on win/Mac that do the same, so why sweat it on this?

[chemlud]

If you have remote installs (remote as in REALLY remote) you need 100% safe DynDNS and to keep downtimes short it's best run on your FW. Not to speak of the fail-over use cases mentioned in the thread above. And DnyDNS services not (adequately?) covered by the new plugin (yet?).

So: Yes, DynDNS can be a show stopper. I saw to my own surprise former forum members posting they have opnsense no longer installed. And a lot of active forum members in the past have become quite in the last months. For me the question is: Quo vadis opnsense?

Especially as the only reason for switching I saw is "old, unmaintained", but the "new" is largely unmaintained, either. So: Lot's to loose, not much to win imho

[allebone]

I posted how I did it via the gui above.