FreeDNS with DynDNS - IP update fails since upgrade to os-dyndns 1.27_1

Started by phaze75, December 16, 2021, 01:05:38 PM

Previous topic - Next topic
I have  issues with the dyndns service. I use FreeDNS. Since the last update of the os-dyndns package to version1.27_1 the update of a changed IP doesn't work anymore. Please find the log entries below:

2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): (Unknown Response)
2021-12-16T01:11:02 opnsense[79456]
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): PAYLOAD: Error 404 : Page not found
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): Current Service: freedns
2021-12-16T01:11:02 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): _checkStatus() starting.
2021-12-16T01:11:01 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org via freeDNS): _update() starting.
2021-12-16T01:11:01 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): running dyndns_failover_interface for wan. found igb0
2021-12-16T01:11:01 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS (freedns.afraid.org): 80.108.241.82 extracted
2021-12-16T01:11:00 opnsense[79456] /usr/local/etc/rc.dyndns: Dynamic DNS: updatedns() starting


The service status shows the value "n/a" in the field "Cached IP". This is awkward as the service seems to extract the correct IP according to the logfile...

Could you please provide suggestions on how to solve this? I am currently relying on manual updates outside the opnsense system.

Can you take a look at https://github.com/opnsense/plugins/issues/2428 ? Some people have issue with v2 URL... this seems to give a clue maybe:

Error 404 : Page not found

It means the URL wasn't found on the server contacted, but not really sure if this is from FreeDNS or some local proxy or something else.


Cheers,
Franci

Yes! Indeed! The version 2 update interface of FreeDNS had been deactivated. Only god knows why...

Now it works flawlessly again! Thanks @franco!