This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 8%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
we want to change the DNS Servers IPs on the Azure VM, when change it manually its back again and everything's got stopped.
Hope the provided information is helpful.
Please 'Accept as answer' if the provided information is helpful, so that it can help others in the community looking for help on similar topics.
Where is your answer?
I hope that my replay is understood
https://learn.microsoft.com/answers/answers/63465/view.html
Please do not forget to "Accept the answer" and Upvote on the post that helps you, this can be beneficial to other community members.
http://www.moamenhany.com
Yes, what is the default DNS servers on the virtual net.?
This a default Azure DNS which provides a naming resolutions based on Azure VM names, you can use it for Host dns query not FQDN.
Any network configuration (DNS, static IP...) must be done from the Azure portal and not from within the VM itself.
This is documented here:
https://learn.microsoft.com/en-us/azure/virtual-network/virtual-network-network-interface#change-dns-servers
--I hope this helps. Please Accept it as an answer and "Up-Vote" the answer or message(s) that helped you so that it can help others in the community looking for help on similar topics
Regards,
Didier3001
Hi,
You need to do that change via Azure portal. Navigate to your VNET, click on DNS servers and enter the DNS server IPs. Then reboot your VM. Then your VM will use the DNS servers which you mentioned over the portal for DNS resolutions.
Do not change it in the guest OS level.
Regards,
Msrini
Unfortunately this effects all VM's i want only to apply it on the production VM's
in that situation you have to split your environment on two or more VNET, or consolidate the DNS services zones on specific DNS Servers which applied on the Virtual Network.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 34%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERR%3C/text%3E%3C/svg%3E)
Hello,
Is it mandatory to reboot the VM in order to apply the new DNS Ip's ? Since taking downtime during the freeze is quite challenging. Please help if we have any alternative.
Thanks & Regards,
Rahul .
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 34%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EIM%3C/text%3E%3C/svg%3E)
@Makkah Mohamed have you been able to resolve your issue ?
As said above you need to define custom DNS servers at VNET level and not at the OS guest level . If you want to apply custom DNS for production VM only you should consider defining another VNET where you can use Azure provided DNS . A workaround would be before this change to use custom DNS at NIC level where the DNS server is 168.63.129.16.
