Each individual machine in an environment have a Persistent external DNS name. For long-time users of CloudShare, this replaces the previously used External Address which would change each time an environment resumed.
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.
The Persistent DNS feature will allow you to switch between servers quickly from a central location, should you want to work in multiple VMs, at the same time, in different windows or on multiple monitors.
External Address vs. Persistent DNS
Accessing machines through the CloudShare web UI has not changed. Clicking ‘View VM’ 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.
1. As with the old External Address, (pubN-NN.env.cloudshare.com), the specific numbers assigned in this string would be refreshed each time an environment suspended.
2. This is not the case with Persistent DNS. You will still see the name listed under ‘External Address, however its reference has changed.
The VM’s DNS name will remain static across Suspend, Resume and Revert actions.
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