built in DDNS OMADA
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I notice the current ver of OMADA displays the public interface of each device per site.
Is it possible to use this feature to have built in DDNS for OMADA sites?
Example, customer has 4 sites, all DHCP WAN internet. If all the sites report public IP to OMADA, and a friendly internal name can be applied to each site. Then when building a VPN, we can use the internal friendly name. And external access can be done via the controllers IP / FQDN, for remote users and such.
Looks like ~70% of the required data is already in place.
Hi @DaKings
Thanks for posting in our business forum.
What kind of version do you use?
Do you mean Public IP Address?
Are you saying we should add a tag (name) to the devices on the Global View page?
If you already have DDNS, you can use the DDNS as the remote VPN IP. Why would the DDNS relate to the "friendly internal name"?
External access to the controller would usually be done by either port forwarding to your local controller or from our cloud platform(omada.tplinkcloud.com)
Are you saying that we should host DDNS for free for customers which they can use the built-in DDNS service we provide?