On 2023-06-09, Grant Edwards <grant.b.edwa...@gmail.com> wrote:
> I agree that having the router/firewall do it is the right way to do it.
>
> I've currently got the app provided by Dynu working.
Interestingly, what the Dynu-provided client does is equivalent to this:
#!/bin/bash
while true
do
curl
http://api.dynu.com/nic/update?username=<...>?password=<...>?hostname=<...>
sleep 120
done
The "/nic/update" command assumes that if you don't provide an IP
address, then it's supposed to use the source IP address of the
incoming TCP connection. It returns a single status string that tells
you if the "update" request resulted in a change, nochange, or failure
of some sort. [IIRC, if the IP changes, it tells you the new IP
address also.] So, the app doesn't faff around trying to determine
if/when the outside IP address has changed or even what that IP
address is.
> I'll soon be switching to a TP-Link ER650 router/firewall when I
> change ISPs. It only supports a few DDNS services, and Dynu isn't
> supported (according to the manual).
According to a recent post in the TP-Link forums, the latest ER605
firmware version has a "General" DDNS provider choice that can be
configured to work with Dynu, so that'll be the long-term solution.
https://community.tp-link.com/en/business/forum/topic/598958
