I use dynu.com...works great
Found this for a windows solution (I guess running on a machine behind the firewall
https://download.cnet.com/Dynu-IP-Updat ... 22952.html
there is ddclient with the "other" option as well
https://www.dynu.com/FAQ/Dynamic-DNS-Service#IPUpdate
As Joulinar said, ddclient is the fastest/easiest way to get it going
Implement DynDNS - dynu.com
Re: Implement DynDNS - dynu.com
dynu windows client works fine, but ddclient on pi only reports the local IP (192.168.2.x)
why is that?
why is that?
Re: Implement DynDNS - dynu.com
because the tool is not detecting external IP correctly? Something to ask developer of this tool
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
Re: Implement DynDNS - dynu.com
Not sure if I find time for next release, but I want a
.
Aside of known and often requested providers like DuckDNS, a custom entry can be used to setup the cron job with any other provider.
dietpi-ddns
that allows to setup multiple DDNS providers which allow to update via simple curl
call via cron job with customisable interval. Everything that requires more, e.g. an own client like No-IP, is not suitable IMO. Looking at the No-IP client, it has not been updated for years, it's CLI is not very intuitive etc, it's simply unnecessary 
Aside of known and often requested providers like DuckDNS, a custom entry can be used to setup the cron job with any other provider.
Re: Implement DynDNS - dynu.com
that is a great idea!!! looking forward to it!