Solved what I am doing wrong (DDNS)

[ttbf_n]

First, I enabled DDNS with asus.com and it worked, created a certificate and all good for a while, then it started intermittently not resolving my ip. Pinging my hostname said unresolved, so probably asus did not return anything at all.

Then, I have registered dynu.com which I know works well (tested with terminal commands on Mac).
Custom inadyn.conf in /jffs/:

custom dynu {
ddns-server = api.dynu.com
ddns-path = "/nic/update?username=%%h&myip=%%i"&password=%%p"
hostname = xxxxxx.dynu.net
username = xxxxxx
password = "md5_hash_of_password"
}
verified with inadyn --check-config -f "/jffs/inadyn.conf"
Then added ddns-start script from documentation and gave it execute permissions.
After applying, log shows no obvious errors, but apparently retries until time out, but dynu.com appears never actually reached:

May 27 15:04:02 watchdog: start ddns.
May 27 15:04:02 ddns: update CUSTOM , wan_unit 0
May 27 15:04:02 ddns: Clear ddns cache.
May 27 15:04:02 custom_script: Running /jffs/scripts/ddns-start (args: my_ip)

and this repeats 5 times, then again 5 times after ~30 minutes or so. I do not see any errors, but no updates at dynu.com. Router shows "registration successful" which I do not understand why.

Any help appreciated, probably I have done something stupid. Thanks.

 

[ttbf_n]

I have done additional tests:

curl -X GET "https://api.dynu.com/nic/update?username=username&password=password_md5" command properly updates the IP at dynu.com

After that, I removed myip part from the ddns-path but no changes.
After, I included username and password directly in the path, but still no changes:
custom dynu {
ddns-server = api.dynu.com
ddns-path = "/nic/update?username=username&password=password_md5"
hostname = username.dynu.net
username = username
password = password_md5
}
* my hostname is same as username.
Looks that dynu.com is not contacted at all. Still the same, after 5 retries it shows "registration successful", when it is clearly not.

Is it somehow possible to simply run the curl command instead of inadyn? If yes, how to manage the reply from dynu?

 

[ttbf_n]

SOLVED. I did not find the issue, but re-installing all the custom setup fixed it. I typed everything exactly as above again, so I do not know what was wrong. Strange though that there were no errors in the log, and it was showing successful registration.
Sorry for unnecessary trouble.