Dyndns updatiing every 5 minutes

Hello, my dyndns is updating every 5 minutes until the limit is reached. I’m using ddnss.de. My Configuration ist ipfire Core 143, the “use classic RED IP address” is checked. Until the limit is reached, it works fine. Have you got any idea?
Thanks a lot
Marcus

I’ve got heaps of ideas.

What’s your problem? Do you run out of possible updates per hour?

In the past there was a checkbox to force update: https://forum.ipfire.org/viewtopic.php?t=5023

Usually there is no need for that, so I think it was removed and an update is supposed to be sent only if the WAN IP actually changed. I wonder that your WAN IP changes every 5 minutes, but if that’s the case and your dyndns provider does not allow unlimited updates there not much you can do about it.

That’s it: there are max.60 updates possible, so that the limit is reached early in the morning. My other ipfire (same dyndns, same configuration) doesn’t update so often.
There is only a button to force an update, I can’t find a checkbox to uncheck.

As I said: there was… in the past.

60 updates per hour / every minute? Or 60 every day / ~2 per hour?

Please post an extract of the dyndns log file here and check your public IP a couple of times per hour just to be sure that your public ip really changed.

60 Updates/day

There is an error reportet in the logfile:

Dynamic DNS update for xxxxxxx.ddnss.de (DDNSS) threw an unhandled exception: Traceback (most recent call last): File “/usr/lib/python3.8/site-packages/ddns /init.py”, line 164, in _update entry(force=force) File “/usr/lib/pyth on3.8/site-packages/ddns/providers.py”, line 158, in call self.update() File “/usr/lib/python3.8/site-packages/ddns/providers.py”, line 182, in update self.update_protocol(protocol) File “/usr/lib/python3.8/site-packages/ddn s/providers.py”, line 648, in update_protocol output = header.getheader(‘ddn ss-response’) AttributeError: ‘HTTPMessage’ object has no attribute ‘getheader’

This is propably just because your service doesn’t allow any more updates and doesn’t even give information back to the script.

Please poste the log until it stops working first. Posting just a single error message won’t show us the whole behaviour.

I’m exspecially interested in the intervall and the information given why it’s going to send updates to your service.

I wanted to post my logfiles, but the system refuses this, because I am a new user and only allowed to post 2 links. So I changed the dots to commas.

The log of ddnss:

Datum / Uhrzeit Remote IP Hosts Update Agent Status Meldung
22.04.2020 05:34 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 05:29 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 05:24 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 05:19 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 05:14 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 05:09 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 05:04 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:59 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:54 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:49 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:44 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:39 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:34 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:29 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:24 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:19 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:14 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:09 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 04:04 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:59 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:54 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:49 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:44 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:39 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:34 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:29 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:24 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:19 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:14 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:09 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 03:04 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:59 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:54 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:49 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:44 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:39 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:34 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:29 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:24 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:19 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:14 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:09 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 02:04 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:59 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:54 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:49 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:44 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:39 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:34 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:29 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:24 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:19 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:14 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:09 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
22.04.2020 01:04 80.154.2.5 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 05:34 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 05:29 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 05:24 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 05:19 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 05:14 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 05:09 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 05:04 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:59 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:54 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:49 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:44 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:39 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:34 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:29 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:24 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:19 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:14 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:09 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 04:04 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:59 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:54 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:49 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:44 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:39 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:34 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:29 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:24 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:19 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:14 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:09 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 03:04 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:59 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:54 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:49 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:44 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:39 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:34 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:29 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:24 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:19 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:14 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:09 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 02:04 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host
21.04.2020 01:59 80.134.1.244 xxxxxxxxxx,ddnss,de IPFireDDNSUpdater/013 Erfolg: Updated 1 host

The log of the dyndns-section of the system-log ipfire contains the same textblock again and again. I can see no other entry than

Dynamic DNS update for xxxxx,ddnss,de (DDNSS) threw an unhandled exception:
Traceback (most recent call last): File “/usr/lib/python3.8/site-packages/ddns /init.py”, line 164, in _update entry(force=force)
File “/usr/lib/pyth on3.8/site-packages/ddns/providers.py”, line 158, in call self.update()
File “/usr/lib/python3.8/site-packages/ddns/providers.py”, line 182, in update self.update_protocol(protocol)
File “/usr/lib/python3.8/site-packages/ddn s/providers.py”, line 648, in update_protocol output = header.getheader(‘ddn ss-response’)
AttributeError: ‘HTTPMessage’ object has no attribute ‘getheader’[quote=“jadokus, post:1, topic:2006, full:true”]

So as we can see most of the updates are totally unessassary because the WAN IP hasn’t changed that often.

I also wonder of that, because this “forces” an update, no matter if the WAN IP has changed or not. That was the checkbox in the past I was talking about (which is gone now).

@arne_f can tell us more :innocent:

This options works only if your RED Interface have your Public IP address. If you have an other router before your IPFire choose the other option.

Hello Arne, this configuration ran over years and I changed nothing. RED knows the puvlic IP-Adress, so that I think, that this part of the configuration is ok. Do you have any other ideas? Thank you!

Is your RED IP the public IP?

Could you please open a ticket on Bugzilla for this?

It looks like a regression from our Python 3 port.

Hello Michael,
ich dont’t have a login to Bugzilla. Is it possible, that you open the ticket?
Thank you!

Your login for this portal works on Bugzilla, too.

My first try failed. I will try again.

Hi,
a bugreport has already been filed
https://bugzilla.ipfire.org/show_bug.cgi?id=12328

Thank you!

I get the same problem after a new install of “ipfire-2.25.x86_64-full-core148”, an update from an older version workes fine.
I patched the
/usr/lib/python3.8/site-packages/ddns/providers.py
by
# output = header.getheader(‘ddnss-response’)
output = response.getheader(‘ddnss-response’)

But as i understood the fix must be in allready. I’m confused.

Martin