Hi,

I've got the client service running on a Windows 10 machine that is rarely rebooted but it seems to fail to update the DDNS record when the IP address changes. It works if I reboot the machine, or even after restarting the Dynu service, but not automatically as I'd expect.

Testing it is tricky, as even restarting the router or powering it off for a while doesn't necessarily result in a new IP address. But correct me if I'm wrong, if I edit the DDNS record manually via the control panel, shouldn't the client automatically reset it back to the correct IP address the next time it polls? I have the polling interval set to 120s and have both the client and engine starting with Windows. The 'Location' field is left empty. Is there another setting I need to look at, please?

The IP update client only detects network changes in the network where the client software is installed. If you change the IP in the control panel, the IP update client does not detect the IP change and will not send an automatic update unless you do a forced manual update.

Thank you for your response xiaoye.

Since restarting the service evidently prompts it to update the record, it clearly can perform that function, so might I suggest you add a setting in a future update to the software, to check that the record matches the network once in every so many polls and updates it as necessary?