topic failing to access DynDNS in My Router

failing to access DynDNS

hml57 — Tue, 13 Dec 2022 16:49:12 GMT

Hello

I have a Plusnet Hub One | Software version 4.7.5.1.83.8.263 .

I use noIP Dyndns service but somehow it's failing to update:

12:02:37, 11 Dec.	(833686.990000) Failed to update NoIP service. Server response: <myhost1.mydomain.net>:4
12:02:37, 11 Dec.	(833686.970000) Failed to update NoIP service. Server response: <myhost2.mydomain.net>:4
12:02:34, 11 Dec.	(833684.300000) Updating NoIP service with IP <myPublicIP> for host myhost1
12:02:34, 11 Dec.	(833684.290000) Updating NoIP service with IP 1<myPublicIP> for host myhost2

I can't any traction with noIP. does anyone use them successfully? I don't know what the error response 4 means

Re: failing to access DynDNS

bobpullen — Tue, 13 Dec 2022 19:13:03 GMT

What is the status of your hostnames if you log into the No-IP website?

You can query the No-IP API directly via a web browser by doing this:

http://<your_noip_username>:<your_no_ip_pasword>@dynupdate.no-ip.com/nic/update?hostname=<your_noip_hostname>&myip=<your_ip_address>

Replacing the obvious bits with the relevant information and removing the chevrons.

If the update is successful then you'll see something like:

good 1.2.3.4

Or maybe 'nochg', indicating that there's been no change to your IP.

If you see a failure when trying to access via web browser then the issue lies with No-IP, or you are using the wrong credentials.

Re: failing to access DynDNS

hml57 — Tue, 13 Dec 2022 21:15:50 GMT

Yes that worked and so my host is now updated.

However, from the router itself http://192.168.1.254, it still fails.

Can I see more than just the Event logs to see more details?

Re: failing to access DynDNS

bobpullen — Tue, 13 Dec 2022 21:49:46 GMT

Are you able to private message me the hub serial number and the account you are using it from? The account I suspect is yours has a Hub One associated with it but it isn't running the firmware version mentioned in your original post

At the very least, we should be making sure the hub is running the latest firmware (although I have never known No-IP to be problematic on any of the Hub One firmwares).