Channels Remote Access doesn't update when public IP changes

Seemingly every time the public IP changes on my home connection, I lose the ability to connect to Channels remotely. I get the message "Remote Access is enabled but we can not reach your server."

When I log in to the server via TeamViewer I see a message in the Remote Access section of General Settings pointing me to Troubleshooting, which then reveals the issue: "x.u.channelsdvr.net is pointed at x.x.x.x but the current IP for this system is y.y.y.y" - and the only apparent way to resolve this is to restart the server. The log shows the same message but nothing else related. I also sometimes see "Could not reach DNS server: lookup resolver-check.u.channelsdvr.net: no such host"

Is there any way to force the server to recognise the change in IP? My DynDNS client updated as expected.

This updates about every three hours, which we’ve considered more than enough of a cadence.

  1. How often is your IP changing?
  2. Is this just the worst luck of all time?
  3. Do you have a way to tell when your IP changed with your other update mechanisms to compare with how long it’s been since it updated?

If you toggle remote access between off and auto it should refresh the dynamic dns

@maddox I've noticed it maybe once every few weeks, so you're right it's probably just bad luck on the timing front. My Dynamic DNS record changed at 17.53, and I posted the original message at 19.25 (both times CEST) so there had been around an hour and a half between the change and me noticing.

@tmm1 Thanks for the tip, I'll try that next time (although I feel like I might have tried that in the past and it didn't seem to work, but it's posible that's a false memory).

It would be great if there was a simple button/link to force it to refresh - especially since the Troubleshooting already recognises it as being incorrect. But if "switching it off and on again" does the trick then that's enough for me!