IP Cloud vs DuckDNS

New HAP AX3 owner and I am trying to learn the MT features and interface.

In my previous setup I was using DuckDNS via pfSense VM. Today I am learning about IP Cloud via MT and that I can have SN###.Domain.com instead.

Is there any reason to use one over the other?

I saw there is a Script on GitHub to handle the DuckDNS in MT console, but I do not know how to use the command line interface yet as a home hobbyest.

For now I only plan on using VPN in from outside the home network when traveling should the need arise. I used to SSH in via port forward, but I figure VPN is better.

Any feedback would be great

Unkis

Personally, I use the SNxxxxx address provided by /ip cloud. That’s 1 fewer script to maintain. And it has been pretty reliable. If you have a domain that you own, you can also create a CNAME subdomain and point it to the SNxxxx one, so you no longer have to remember the router’s serial number.

There’s also the Back-to-Home feature if you don’t want to tinkle with the configurations of VPNs manually.

Rarely but it does happen where IP cloud is not available, in that case a backup is not a bad idea. But yes IP cloud is very handy.

All,

Thanks for the feedback. I will try and give IP Cloud a try then, seems quite simple and learn something new.

Thank you,

Unkis

As an example I have a mikrotik that I reach at a remote location,
In my firewall address list I put the IP Cloud URL name=RemoteRouter

Then in rules I can use interface-list=RemoteRouter and my local router resolves that for me. Very handy