dyndns clients sending 1 update request / second even if they only ever get an error response.


Got some explanation via email:

the filesystem on the client was full and that triggered this misbehaviour of the dyndns update client.

So, if you code some update client and you can't write to disk any more, don't DOS the dyndns service because of that, but rather terminate (or slow down a lot).

Sign in to participate in the conversation - because anarchy is much more fun with friends. is a small Mastodon instance for and by the Chaos community surrounding the Chaos Computer Club. We provide a small community space - Be excellent to each other, and have a look at what that means around here.
Follow @ordnung for low-traffic instance-related updates.
The primary instance languages are German and English.