update DNS settings for VNET without restart of the VMs to take effect
Current when we try to update the DNS settings in the VNET or NIC, it required the VMs to be restarted to take effect. But when there are a large amount of VMs under the VNET, it would be a hard work to do so.
If this process could be simplify so that the restarted of VM will be no longer required, it would be a good news.
Anonymous
shared this idea
Thank you for the feedback. We’ll look into whether this can be included in our roadmap.
7 comments
-
Craig
commented
what's the status with this? It's been TWO YEARS! We don't have to do this with windows VMs in AWS, why do we have to do it in Azure?
-
Devin
commented
Why is this still an issue? Come on Microsoft, this is really causing issues, and it has been known by you for over two years. Wake up and get it fixed. At least provide an update to your userbase....
-
Hebert Viana
commented
Hello guys,
Is Microsoft working on a way to prevent this restart? -
Tommy Kuter
commented
Hi,
I can confirm this.
We need to update our secondary DNS configuration on about 200 VMs, and i just realized like you that a restart is needed.It would be nice to see Microsoft working on this.
-
Hernán Fonseca
commented
besides it's really annoying restarting +100 vms after changing the dns values on the vnet, also sometimes the new values are not been acquired after the vms are restarted so, you'll probably end up doing several restarts of your vms. how adorable is this?
-
Jag Sandhu
commented
Hi,
Is there any update for this? We will be changing our internal DNS servers, and dont fancy rebooting 100+ servers to get the new DNS address from the Vnet. -
Alex Leong
commented
It is not practical every time making just a small change to update the DNS setting in the VNET or NIC and it required the VMs to be restarted in order to take effect. It would be great if Microsoft can simplify the process.