User Guide - Using a domain name for a load-balanced private service
Owen is the IT manager of a company that is already using OpenVPN Cloud. The R&D team has been working on a new web application and have requested that Owen make the web app available to trial users as a beta release. The R&D team doesn't want to expose the application to the internet because it is still being worked on and may have security holes.
Owen decides that the best approach is to treat the app as an internal application and allow the trial users to access it via OpenVPN Cloud.
- Owen creates a Host and assigns a domain name of testapp.internal.net
- He then creates multiple Connectors for the host (one for each of the application’s web servers) and installs the Connector on each web server.
- He then adds a User Group and adds the trial users as Users in this group.
- Since the VPN topology has already been set to Custom, he adds an Access Group to provide access to the trial user group for only the Host with the domain name of testapp.internal.net
The R&D team provides their trial users with the URL testapp.internal.net, but instructs the users to first connect to OpenVPN Cloud to be able to access the URL.
When the trial users connect to OpenVPN Cloud, they can only access testapp.internal.net and the traffic to the web app is routed in a round-robin fashion among all of the Connectors / web servers that are configured for the Host.