SOLVED

DNS Name... Any way to change this?

%3CLINGO-SUB%20id%3D%22lingo-sub-66613%22%20slang%3D%22en-US%22%3EDNS%20Name...%20Any%20way%20to%20change%20this%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-66613%22%20slang%3D%22en-US%22%3E%3CP%3EShort%20funny%20story.....%20A%20VM%20I%20had%20been%20using%20decided%20that%20it%20didn't%20want%20to%20take%20the%20upgrade.%26nbsp%3B%20So%20instead%20of%20fighting%20it%2C%20since%20it%20was%20broken%20and%20I'm%20not%20the%20kind%20to%20cry%20over%20exploded%20VMs%2C%20took%20the%20important%20data%2C%20and%20blew%20away%20the%20VM.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20trouble%20was%20not%20in%20recreating%20the%20VM%2C%20or%20restoring%20the%20data%2C%20network%20security%2C%20or%20any%20of%20that.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20trouble%20I'm%20having%20is%20the%20DNS%20name%20has%20now%20changed.%26nbsp%3B%20From%20*.cloudapp.net%20to%20now%20*.southcentralus.cloudapp.azure.com...%26nbsp%3B%20I%20realize%20this%20has%20to%20do%20with%20the%20location%20of%20the%20data%20center%2C%20but%20what's%20the%20simple%20answer%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDo%20I%20move%20it%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDo%20I%20delete%20it%20and%20recreate%20it%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20that's%20the%20case%2C%20which%20data%20center%20has%20the%20*.cloudapp.net%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOr%20is%20it%20possible%20to%20create%20a%20virtual%20network%20or%20virtual%20domain%20name%20to%20point%20my%20vm%20back%20to%20a%20*.cloudapp.net%20DNS%20name%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMany%20thanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-66613%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EVirtual%20Network%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67818%22%20slang%3D%22en-US%22%3ERe%3A%20DNS%20Name...%20Any%20way%20to%20change%20this%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67818%22%20slang%3D%22en-US%22%3EExcellent%20response%20and%20very%20understandable.%20Thank%20you!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67406%22%20slang%3D%22en-US%22%3ERe%3A%20DNS%20Name...%20Any%20way%20to%20change%20this%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67406%22%20slang%3D%22en-US%22%3E%3CP%3Ehave%20a%20look%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-resource-manager%2Fresource-manager-deployment-model%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConsider%20ARM%20to%20be%20V.2%20Azure%2C%20there%20are%20many%20advantages%20to%20ARM.%3C%2FP%3E%3CP%3Ea%20few%20of%20the%20advantages%2C%20is%20easier%20deployment%20through%20Resource%20templates%2C%20greater%20flexibilty%20when%20you%20want%20to%20change%2C%20cheaper%20prices%20when%20using%20a%20Cloud%20service%20Provider.%3C%2FP%3E%3CP%3EBut%20MS%20has%20no%20plans%20for%20setting%20an%20end%20of%20life%20for%20V1%20anytime%20soon%2C%20so%20Yes%20if%20you%20recreate%20the%20VM%20as%20a%20V1%20machine%20you%20can%20use%20the%20old%20DNS%20suffix.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67216%22%20slang%3D%22en-US%22%3ERe%3A%20DNS%20Name...%20Any%20way%20to%20change%20this%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67216%22%20slang%3D%22en-US%22%3EKent%2C%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20for%20the%20reply%20and%20the%20explanation%20-%20I%20have%20to%20learn%20more%20about%20the%20%22ARM%20based%20VM%2FPublic%20IP%20DNS%20name%22%20-%20any%20resource%20you%20know%20of%20you%20could%20shoot%20my%20way%3F%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20difficulty%20is%20not%20in%20forwarding%20from%20my%20main%20DNS%20to%20the%20cloud%20DNS%20name%2C%20it's%20that%20I%20have%20a%20tool%20that%20packages%20agents%20up%20to%20deploy%20and%20points%20to%20its%20known%20DNS%20name%20through%20a%20self-test.%20I%20suppose%20there's%20some%20sort%20of%20way%20to%20change%20that%20process%20but%20I%20doubt%20I'll%20get%20far%20with%20it.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20I%20recreated%20it%20as%20a%20%22Classic%20VM%22%2C%20would%20I%20get%20the%20*cloudapp.net%20DNS%20name%20again%3F%20What%20brief%20advantages%20are%20there%20from%20ARM%20against%20Classic%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-67022%22%20slang%3D%22en-US%22%3ERe%3A%20DNS%20Name...%20Any%20way%20to%20change%20this%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-67022%22%20slang%3D%22en-US%22%3E%3CP%3ECloudapp.net%20would%20indicate%20you%20where%20using%20a%20Classic%20VM%20in%20a%20cloud%20service.%3C%2FP%3E%3CP%3EWhat%20your%20are%20creating%20now%20is%20an%20ARM%20based%20Public%20IP%20dns%20name%20that%20can%20be%20assigned%20a%20ARM%20based%20VM%20network%20card.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eregardless%20of%20what%20you%20choose%2C%20i%20would%20strongly%20suggest%20you%20use%20CNAME%20records%20in%20a%20domain%20that%20you%20own%2C%20this%20way%20no%20matter%20what%20you%20change%20in%20you%20azure%20infrastructur%20the%20the%20records%20in%20you%20own%20DNS%20can%20be%20updated%20to%20the%20new%20resource%20with%20out%20having%20to%20inform%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

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?

 

Many thanks!

4 Replies

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.

Kent,

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?
best response confirmed by Daniel Martins (Microsoft)
Solution

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.

Excellent response and very understandable. Thank you!