DynDNS

[macgd016]

My rather old home heating system requires a static IP address to access it remotely, until now I've been running DuckDNS on my PC to manage this but I've recently subscribed to SurfShark VPN and find that DuckDNS is picking up the SurfShark IP instead of the router IP so I need a new, and preferably free, way forward.

I find that NoIp is one of the DynDNS options in my FAST5364 3.00 (SG4K100208) but when I put my NoIP credentials in I get a Status error.  Have I got something wrong or is this no longer supported I wonder?

[Philile-TT]

Thank you for the support @KeithFrench 

[macgd016]

I think that's quite likely Keith 👍

[KeithFrench]

Perhaps this is for newer customers, where older ones like me do not need to do this, as I already have an account with No-IP.

[macgd016]

Interestingly NoIP's getting started guide https://www.noip.com/support/knowledgebase/free-dynamic-dns-getting-started-guide-ip-version also refers to the need to set up a DDNS key

Article Summary

• Create a free No‑IP account and confirm your email.
• Add a hostname (A‑record) linking to your current public IPv4 address.
• Enable Dynamic DNS and generate a DDNS Key (username & password) for your hostname.
• Configure a device (router, camera, DVR) or install the No‑IP Dynamic Update Client (DUC) to send IP updates automatically.noip.com
• Verify your hostname updates correctly when your public IP changes.

[KeithFrench]

Fair enough. So long as you have tested that it works when the WAN IP address changes.

[macgd016]

There's no more I can say, you have far more knowledge than I have on these things, I'm just a dabbler looking for a solution.  All I can say is I first tried using my Username & Password for my NoIP account together with the host address I'd set up and this didn't work.  I then read their router setup instructions and followed them and it did work so I'm happy.

[KeithFrench]

Hi @macgd016 

I have just deleted my No-IP & put it back in, no problem.

[KeithFrench]

OK, yes, that was because I took the screenshot before applying the changes. This is my current on the Hub 3, which is basically the same:-

DDNS

[macgd016]

I tried that first but they didn't work for me, I had to use the keys as advised by NoIP for all routers.  Is it possible NoIP have changed their requirements.

PS. Your screen shot shows your connection as Disabled

[KeithFrench]

Hi @macgd016 

On the Sagemcom, there is no need for any keys at all.

Username & password: the credentials used by your No-IP account online.

Hostname: full No-Ip DDNS domain

No-IP

[macgd016]

I found this on the NoIP support pages: https://www.noip.com/support/knowledgebase/how-to-configure-ddns-in-router

Where it says

DDNS/Service Provider: No-IP
Username: Your DDNS Key Username / Email
Password: Your DDNS Key Password
Hostname/Domain: all.ddnskey.com

I'm no expert in these things but this worked for me 😁

[KeithFrench]

I have never had to set up any keys.

[macgd016]

Hi Keith

Thanks for the input.

I think I have NoIP working now but it wasn't as straight forward as I'd expected on the NoIP side.  It all seemed to be simple to start with as the router asks for Provider, User Name, Password and Hostname which I assumed to be NoIP, the username & Password used to log into NoIP, and hostname.ontheweb.com. 

However there seems to be another step withing NoIP you have to do which is to set up your DDNS Keys.  This is reasonably easy but this gives you a different Username and the password is the DDNS Key you are given, the Hostname is the hostname you setup at the start which is something like hostname.ontheweb.com.

Hopefully this might be helpful to someone trying to use NoIP in the future. 

[KeithFrench]

Hi @macgd016 

No-IP works fine with the Sagfemcom hubs. When you connect to any VPN, you are allocated an IP address for your device on their network, with whatever their public IP address is, so that will never work.

With No-IP, are you putting the username & password required to log into your account on their portal? The Hostname needs to be the full No-IP DDNS domain.