dns name label re-use

Dave Roberts 116 Reputation points
2021-06-15T02:11:27.37+00:00

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 DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
593 questions
Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,130 questions
0 comments
Accepted answer
  1. Dave Roberts 116 Reputation points
    2021-06-15T18:37:31.913+00:00

    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

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. TravisCragg-MSFT 5,676 Reputation points Microsoft Employee
    2021-06-15T04:59:52.17+00:00

    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.