Unfortunately, the DDNS service is not updating anymore. In DietPi-DDNS there are the following logs:
Nov 16 16:20:07 DietPi CRON[101840]: pam_unix(cron:session): session closed for user dietpi-ddns
Nov 16 16:20:07 DietPi dietpi-ddns[101847]: curl: (23) Failure writing output to destination
yes, the logs are actually shown in dietpi-ddns. I can apply my settings and the test succeeds. But as soon as CRON tries to update the ddns status, it fails.
What’s very strange, Dynv6 is showing me regular updates on their website/dashboard. Somehow, dietpi-ddns is still connecting to their server. But as soon my ip adress changes, I loose connection to my dietpi nas from outside. I have to manually refresh my ip adress on dynv6’s website.
First of all, you’re affected by this bug: Cannot had more than one No-Ip domains · Issue #5830 · MichaIng/DietPi · GitHub
However, the actual DDNS update should still succeed, only writing the response to a file fails (which is not intended and fails, luckily, due to insufficient permissions of the service user). However, to fix the file:
sed -i 's/^curl -6or4/curl/' /var/lib/dietpi/dietpi-ddns/update.sh
I’ll add this patch for the upcoming DietPi update latest today.
Thanks all for your help. After your fix @MichaIng I get this logs in dietpi-ddns:
Nov 20 11:00:14 DietPi CRON[9518]: pam_unix(cron:session): session closed for user dietpi-ddns
Nov 20 11:00:01 DietPi CRON[9521]: (dietpi-ddns) CMD (/var/lib/dietpi/dietpi-ddns/update.sh)