Messages

Found a hint to the issue in the Azure Activity Log. In the case of Azure, the host name defined in the dyndns configuration must not be specified as the FQDN and the record set needs to exist for os-dyndns to update it. It doesn't create the record but just throws and exception in the Azure Activity Log.

It would be nice if the os-ddclient log would also display these error messages.

Hi,
I upgraded and replaced the legacy ddclient with the new one using the native OPN backend. I configured azure as update target filling all the parameters necessary. According to the log the plugin can successfully connect but the result in the log is always: "Account cade455-************ [azure - ] not modified". On the Azure side it doesn't create or update the specified hostname.

I tried many things but could not make it work with Azure as service. Some additional details:
- Intentionally providing an incorrect app ID or secret results in the expected error message in the log file.
- I deleted the cache file of the old ddclient plugin.
- The new plugin using aws as "service / provider" works without issues.

OPNsense version: 24.1.7_4-amd64
os-ddclient version: 1.21_2

Does anyone have an idea on how to make this work or is the new dd-client in combo with Azure, broken?

Thanks in advance!