question

DaveRoberts-9137 avatar image
0 Votes"
DaveRoberts-9137 asked DaveRoberts-9137 answered

dns name label re-use

Hi, I just had a situation where my VM became unresponsive, I couldn't restart it, or shut it down from the portal so I created a new vm from a snapshot of that one made a month or so ago. However, I need the dns label of the public ip to resolve now to the new VM. I changed the old public ip resource to have no configured dns name, but now when I try to assign that name to the new VM's public IP it gives me the message that the "dns label is not available. Try using a different label".

In a previous question I saw that someone answered that it may take some time to free up. But it has been a few hours now. Is there some other asset hidden away that is locking that label? Going to a new label is not really an option. Do I need to delete the old resources? I have tried to delete the old VM's NIC resource, but that throws an error.

Any ideas are very much appreciated!
Dave

azure-virtual-machinesazure-dnsazure-virtual-machines-networking
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DaveRoberts-9137 avatar image
0 Votes"
DaveRoberts-9137 answered

UPDATE: The long and short of it is that there was some kind of service interruption(s) on WestUS2. This resulted in my reboot/restart/delete failures and then also meant I couldn't move the public IP to my new VM (which did create -- but slowly). This morning I was able to quickly assign the DNS label I need and it all worked as expected.

  • I wasted a LOT of time because there was a service problem on WestUS2, but all the status indicators on the Azure status page said - for hours - that WestUS2 had no issues when it actually was a wreck. Not good enough. **

resolved now

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

TravisCragg-MSFT avatar image
0 Votes"
TravisCragg-MSFT answered DaveRoberts-9137 commented

This can take a few hours to free up, but in my experience rarely takes more than an hour. If this takes more than 12, you can try to create a support request.

In the future, your best bet is to reserve the DNS name on the Public IP as you did, and then switch that Public IP resource (with the existing reserved DNS name) to the NIC of the new VM. You can then create a new Public IP resource for the old NIC if needed. This way creates only seconds of downtime during the PIP swap.

· 5
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HI Travis - thanks for the reply.

My usual process is to migrate the public ip by removing from one vm then assigning to the other, however in this case the whole vm seemed to be inaccessible. I couldn't start/stop/restart/redeploy or delete it or its resources. I would just get a "retryable error". Despite the green lights up and down the service status page I think Azure was having some issues. To create a new VM from my existing snapshot took approximately 25 minutes.

As for trying again now.. I can't even log in to portal.azure.com at this exact moment. The page doesn't come up. That can't be good.

Is there any way to see what resource might be still attached to the dns label I want to use? A reference finder or some other tool?

DR

0 Votes 0 ·

Strange, in most cases you will still be able to stop the VM. There is an outage in West US 2 currently that will prevent you from doing basic management operations on your VM.

You can try to get the VM using PowerShell / Azure CLI, or use resources.azure.com to view your VM.


0 Votes 0 ·

Ha. WestUS2 is where I am operating. This afternoon during all the troubles it was still showing all green lights.

I guess waiting is my option right now. Thanks for the heads up.
DR

0 Votes 0 ·
Show more comments