freedns.afraid.org fails to update after coreupdate from 159 >> 160 gives endless log entries: DDNSNotFound: Not found
Additionally adding an alternative provider; tested with noip.com gives success and updates however but throws a log exception: Dynamic DNS update for xxxxxx.hopto.org (NoIP) threw an unhandled exception: Traceback (most recent call last): File /usr/lib/python3.8/site-packages/ddns /system.py, line 272, in get_address return self.__addresses[proto] KeyErro r: ‘ipv4’ During handling of the above exception, another exception occurred: Traceback (most recent call last): File /usr/lib/python3.8/site-packages/ddns /init.py, line 178, in update entry(force=force) File /usr/lib/pyth on3.8/site-packages/ddns/providers.py, line 157, in call elif self.has failure or not self.requires_update: File /usr/lib/python3.8/site-packages/dd ns/providers.py, line 202, in requires_update if self.ip_address_changed(se lf.protocols): File /usr/lib/python3.8/site-packages/ddns/providers.py, line 270, in ip_address_changed current_address = self.get_address(proto) File /usr/lib/python3.8/site-packages/ddns/providers.py, line 329, in get_address return self.core.system.get_address(proto)
(In reply to Ian bryant from comment #0) > freedns.afraid.org fails to update after coreupdate from 159 >> 160 gives > endless log entries: 07:11:03 ddns[27635]: Not Found 07:11:03 ddns[27635]: DDNSNotFound: Not found 07:11:03 ddns[27635]: Dynamic DNS update for xxxxxx.mooo.com (freedns.afraid.org) failed:
I can confirm the same issue with freedns.afraid.org on my setup after upgrading from 159 to 160.
Does anyone have a longer log message or is what was already posted all that can be seen?
I've not anything more relvant in the logs. If I invoke from cli "ddnsctrl update-all" the only reply is "DDNSNotFound: Not found" Also I can confirm that it seems specific to freedns.afraid.org because I've tryed dedyn.io and it works fine
In the last release, freedns.afraid.org was updated to their new API and it was reported back to us that it works fine. Looks like it doesn’t.
> https://community.ipfire.org/t/dynamic-dns-doesnt-work-for-some-ddns-providers-after-core-update-159-160/6397/24?u=ms Sounds like there is no bug here, just a confirmation issue on the provider side.
After changing the Token unfortunately the automatic update for freedns.afraid.org fails to update correctly on an Ip change If you run ddns -d update-all --force It runs correctly , However a normal IP change update fails to run and the log reports: 07:25:00 ddns[27307]: Further updates will be withheld until 2021-10-22 16:20:04.595146 07:25:00 ddns[27307]: DDNSUpdateError: The update could not be performed 07:25:00 ddns[27307]: Last failure message: 07:25:00 ddns[27307]: An update has not been performed because earlier updates failed for xxxxxx.mo oo.com Itlooks like it is holding off the update for 12 hours irrespective of an ip change Br Ian
All seems to work A-OK with Core Update 162. I needed to update freedns.afraid.org to Version 2 and change my token info. Once that was done it all worked as expected. I also added a wiki page to help others with freedns.afraid.org: wiki.ipfire.org - Additional info - FreeDNS