May 02 2017 06:35 PM - last edited on Aug 18 2017 02:31 PM by Eric Starker
Short funny story..... A VM I had been using decided that it didn't want to take the upgrade. So instead of fighting it, since it was broken and I'm not the kind to cry over exploded VMs, took the important data, and blew away the VM.
The trouble was not in recreating the VM, or restoring the data, network security, or any of that.
The trouble I'm having is the DNS name has now changed. From *.cloudapp.net to now *.southcentralus.cloudapp.azure.com... I realize this has to do with the location of the data center, but what's the simple answer?
Do I move it?
Do I delete it and recreate it?
If that's the case, which data center has the *.cloudapp.net?
Or is it possible to create a virtual network or virtual domain name to point my vm back to a *.cloudapp.net DNS name?
May 04 2017 04:48 AM
Cloudapp.net would indicate you where using a Classic VM in a cloud service.
What your are creating now is an ARM based Public IP dns name that can be assigned a ARM based VM network card.
regardless of what you choose, i would strongly suggest you use CNAME records in a domain that you own, this way no matter what you change in you azure infrastructur the the records in you own DNS can be updated to the new resource with out having to inform users.
May 04 2017 09:39 AM
May 04 2017 10:54 PMSolution
have a look here.
Consider ARM to be V.2 Azure, there are many advantages to ARM.
a few of the advantages, is easier deployment through Resource templates, greater flexibilty when you want to change, cheaper prices when using a Cloud service Provider.
But MS has no plans for setting an end of life for V1 anytime soon, so Yes if you recreate the VM as a V1 machine you can use the old DNS suffix.