One way you can connect to a CloudShare VM is via an RDP client using the VM's external address, which is a persistent external DNS name assigned to each VM in a CloudShare environment.
(Clicking ‘View VM’ in the environment details page is still the best method for actively working on a specific machine as this is how we keep your environment running. CloudShare also accelerates this RDP connection to improve overall performance.)
Each individual machine in an environment has a persistent external DNS name called external address. The external address remains static across Suspend, Resume and Revert actions.
This means you can bookmark or save the RDP link and not worry about the IP changing. For example, when using remote desktop connection managers or terminal services such as MSTSC, you can access that VM with the machine name instead of the External Address. This will also maintain a VM’s external name (FQDN) for the lifetime of the environment.
External Address in the CloudShare Web UI
To grab the external address of a VM, open the environment's Environment Details page, scroll down to the VM, click More details and you'll see it listed as External Address.
NOTE: When first launching an environment, it may take up to five additional minutes to assign the persistent DNS once the environment is listed as ‘Ready’. Soon after the address is generated, it will temporarily have a dummy underlying IP address, which will automatically update once it is prepared.
Setting up Persistent DNS
There is nothing you need to do as CloudShare handles this automatically. The Persistent DNS will be retrieved as part of machine details when creating, launching or resuming an environment. >
Persistent DNS and Vanity URLs
- Each machine in your environment have an automatically generated DNS name
- You can set a vanity name for one VM in your environment. The DNS name for this VM will be based on this vanity name. For example if your vanity URL is http://my_vanity.cld.sr, the FQDN of this VM is my_vanity.vm.cld.sr
- You can also set up an alias for the DNS and CNAME to a machine
- While the FQDN will remain the same, the underlying IP address will change as the environment suspends and resumes
- As always, machines in your environment will have to be running for you to access them directly via the persistent DNS. In conjunction with CloudShare’s API (in TeamLabs and Enterprise), you can resume and manage your environment remotely
- You can set a DNS alias (CNAME) with your own domain name pointing to your CloudShare VM Persistent DNS
For Long Term CloudShare users
If you are a longterm CloudShare user, you might remember VM's having external addresses with the format pubN-NN.env.cloudshare.com, in which the specific numbers assigned in this string would be refreshed each time an environment suspended. This format was replaced with the newer persistent format.