Forum Discussion
DNS Name... Any way to change this?
- May 05, 2017
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.
Thanks for the reply and the explanation - I have to learn more about the "ARM based VM/Public IP DNS name" - any resource you know of you could shoot my way?
The difficulty is not in forwarding from my main DNS to the cloud DNS name, it's that I have a tool that packages agents up to deploy and points to its known DNS name through a self-test. I suppose there's some sort of way to change that process but I doubt I'll get far with it.
If I recreated it as a "Classic VM", would I get the *cloudapp.net DNS name again? What brief advantages are there from ARM against Classic?
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.
- Peter BarclayMay 07, 2017Copper ContributorExcellent response and very understandable. Thank you!