ddclient icon indicating copy to clipboard operation
ddclient copied to clipboard

FreeDNS: update to the new token based (version 2) of the dynamic update interface

Open NvrBst opened this issue 3 years ago • 0 comments

The FreeDNS update does work currently. But you have to use the old global_account username/password IP update method: - http://sync.afraid.org/u/?u=[username]&p=[password]&h=[host]&ip=12.12.12.12 - http://[USERNAME]:[PASSWORD]@freedns.afraid.org/nic/update?hostname=[DOMAIN]&myip=[IP]

This is fine, which saves your full login credentials in plain text on the router. But there is a method which doesn't require this anymore, just the simple "Randomized Update Token" FreeDNS gives, which has both the [hostname] and [login/pass] and [IP] built-in. This is by far more simple and more secure. Considering if you do have an attack, a malicious user would only be able to update that single IP, and not access your complete FreeDNS account, where they could delete everything.

The sync address for this is simply: http://sync.afraid.org/u/[randomized_update_token]/

Some Info on the new method: https://freedns.afraid.org/dynamic/v2/tips/

Is there a way to add this to ddclient, namely if only one (username or password) is given use the new method. But if both are given, then use the old method. Or just make a new SERVICE, "FreeDNS (v2-token)". Although I think the token method should be the default, since this is what most users would/should use.

The old method is still useful for some users, but the new methods does allow for most things (can link the same token to multiple hosts thus updating multiple hosts with 1 command, and can still include the ?ip=[IP] to disable the server-side IP detection, and use whatever remote IP detection you want.

NvrBst avatar Jun 11 '22 00:06 NvrBst