Dynamic DNS doesn't work for some DDNS providers after core update 159 -> 160

Hello,

After core update 159 to 160, I realize that the ip was not updated in freedns.afraid.org service. I checked the credentials in that service and it has not changed.

Maybe it’s a bug? With core 159 was working perfect.

Thank you.

2 Likes

I have the same problem and it is not resolved !
freedns.afraid.org fails gives endless log entries of:

Log extract:

13:50:00 ddns[21213]: Further updates will be withheld until 2021-10-07 15:22:58.243357
13:50:00 ddns[21213]: DDNSNotFound: Not found
13:50:00 ddns[21213]: Last failure message:
13:50:00 ddns[21213]: An update has not been performed because earlier updates failed for xxxxx.mo oo.com
13:45:00 ddns[21048]: Further updates will be withheld until 2021-10-07 18:41:51.690926
13:45:00 ddns[21048]: DDNSNotFound: Not found

I then temporarily made a noip.com one this seems to have worked but throws exceptions in the log:

Log Extract: ( Note domain name changed to protect)

14:20:29 ddns[24939]: Dynamic DNS update for XXXXXX.hopto.org (NoIP) successful
14:20:28 ddns[24939]: Further updates will be withheld until 2021-10-07 15:22:58.243357
14:20:28 ddns[24939]: DDNSNotFound: Not found
14:20:28 ddns[24939]: Last failure message:
14:20:28 ddns[24939]: An update has not been performed because earlier updates failed for xxxxx.mo oo.com
14:20:00 ddns[23933]: 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)

I’m going to test again, maybe my conclusion was wrong.

You are right Ian, maybe my error was login to afraid.org page, so the ip was updated checking their update scripts.

This is what I got some minutes ago:

09:06:42 ddns[2649]: Dynamic DNS update for cxxxx.net (freedns.afraid.org) failed:
09:06:42 ddns[2649]: DDNSNotFound: Not found
09:06:42 ddns[2649]: Not Found
09:07:47 ddns[3186]: An update has not been performed because earlier updates failed for cxxxxx.net
09:07:47 ddns[3186]: Last failure message:
09:07:47 ddns[3186]: DDNSNotFound: Not found
09:07:47 ddns[3186]: Further updates will be withheld until 2021-10-08 00:06:42.367282
09:10:00 ddns[3443]: An update has not been performed because earlier updates failed for cxxxxx.net
09:10:00 ddns[3443]: Last failure message:
09:10:00 ddns[3443]: DDNSNotFound: Not found
09:10:00 ddns[3443]: Further updates will be withheld until 2021-10-08 00:06:42.367282
09:10:20 ddns[3568]: An update has not been performed because earlier updates failed for cxxxxx.net
09:10:20 ddns[3568]: Last failure message:
09:10:20 ddns[3568]: DDNSNotFound: Not found
09:10:20 ddns[3568]: Further updates will be withheld until 2021-10-08 00:06:42.367282

It’s not working.

How can I delete “SOLVED” in the title of the original post?

Hi Feles, I think you should also remove your line that says “EDIT: A rectification, it was an issue with freedns.”
people will read the first post and think its a issue with freedns , Which it clearly is not !

Hi Ian,

Sadly I can not edit the message, I don’t know why, maybe I’m in a category that doesn’t permit edit the posts after some days. If an admin can do it, please.

Meanwhile the problem persists. I updated the ip manually in the freedns page, that was the point of confusion because in the ipfire gui the domain appears in green.

Having this problem for freedns also, I’ve edited the heading.

Thanks Bernhard. Maybe the last phrase “EDIT…” must be removed as Ian said in the original post. Sorry for the inconveniences.

I’ve done. :wink:

Thank you very much

The reason the name appears in the DYDNS page as green is because at the time you are checking it the IP of the WAN matches that of that DNS name it has queried… Its not related to if it is doing the update correctly just the fact it currently matches ( because you made the manual update) in mine the afraid one shows red as I did not update it and the WAN Ip does not match the current Ip registered for that name.
I have switched to the Noip one I mentioned in my earlier post, that works ( to a fashion ) although its flooding the logs with rogue entries as I reported before!

I understand. Reading the log I see that nothing has changed, is the same “…DDNS Not found…”

Could be the possibility that the change to python3 has something to say?

I’m not a programmer, but the fact is that this was working perfect in core 159.

I don’t think so. The ddns package was changed to a python3 version in Core Update 142.

It is not a totally generic issue as I am running with dynu.comI have a fixed IP so what I did to test it was to change my IP address in dynu.com and my entry in the IPFire DDNS WUI page went red.

I then ran the instant update and the entry in IPFire went green and in dynu.com the IP address was updated to the correct one.

Looking through the ddns git repository I see that in July there was a commit for a modification of the freedns.afraid.org entry in the providers.py file to update it to use the new provider API.

The version of ddns was updated from 013 to 014 and that new ddns version was installed into Core Update 160.

I think this looks like it should be raised as a bug. Your IPFire People email address and password work for logging in to the IPFire bugzilla site.
https://bugzilla.ipfire.org/

Wiki entry on raising bugs.
https://wiki.ipfire.org/devel/bugzilla

1 Like

Thank you very much Adolf.

Please see my entries also noip causes excesses chatter on the logs

Do you get a clean entry for this in your logs? Using noip I get an exception

Changed the heading again.
Don’t forget to open/update the BugZilla ticket.