Using Dynamic DNS with TransPorts

Dynamic DNS maps a certain hostname to the current IP address of a device, and updates the mapping if and when the IP address changes.  This is useful to ensure a device can still be accessed even if its IP address is unknown, for example, because it's Dynamic and may change.

At the time of this writing, TransPorts are compatible with No-IP.com and Dyn.

With respect to TransPorts, in the cellular space, Dynamic DNS is best suited for "Mobile Terminated" cellular provider plans that provide public, Dynamic IP addresses for the mobile interface.  Mobile Terminated plans are bi-directional, meaning traffic is allowed  both outbound (from the TransPort out) and inbound (to the TransPort and devices attached to it).  Although a Static IP address will work just fine, using Dynamic DNS would be somewhat redundant since that Static IP would never change.

Note that with a "Mobile Originated" cellular provider plan, you may able to register the IP with the Dynamic DNS provider, however you will not be able to reach the TransPort - or anything attached to it - through the Internet cloud.  This is because Mobile Originated plans are outbound only.

Some providers only offer mobile originated plans, so Dynamic DNS isn't suggested in these environments.  Also ensure that your mobile IP address is a public IP address, not a private (NAT'ed), for Dynamic DNS to work as intended.

Finally, please note that Private plans (i.e. - No internet connectivity) will not work with Dynamic DNS either.