Looks like the type check was off leading to update an empty address.
Now instead check first and throw a warning. The condition might be
transient but try to hint at the user that the setup is likely broken.
Configuration variables applicable to the 'freedns' protocol are:
protocol=freedns ##
server=fqdn.of.service ## defaults to freedns.afraid.org
login=service-login ## login name and password registered with the service
password=service-password ##
fully.qualified.host ## the host registered with the service.
* Remove the "default" handling for backend: it was properly migrated and
is required. It will make flipping to the native backend easier later.
* Make the ddclient.conf file easier to read: global block, then one block
for each account.
* Adjust the templating to sprinke missing "\" at the end of the line and
replace hardcoded values where we can easily use service.name.
Switching back and forth between backends is a bit annoying as the other
backend can break using the correct account data from the other one, because
not all the services are shared equally between the two.
Maybe long term it would be better to build a plugin variant for ddclient
and dyndns so we could revive os-dyndns and just share the code in this one
directory. The backend switch would then be carried out over which plugin
is installed a bit similar to what WireGuard is doing.
selectattr seems like a good way to fix this. While here reformat the JSON
and fix an error with empty stats causing a number of API errors being thrown.
Explain __MYIP__ and __HOSTNAME__ usage in server help text, while here add some missing @staticmethod decorators in various accounts. Make sure the server fields either validates a domain or an uri, depending on the protocol selected.
Franco Fichtner
Greg GlocknerandGitHub
Clemens HardewigandGitHub
Ad Schellevis
Rhys BarrieandFranco Fichtner