Last month we looked at how to set up nested VMs in Hyper-V on Windows Server 2016. Azure, of course, runs on Hyper-V and some regions already have some of their hosts upgraded to Windows Server 2016.

As Brien recently discovered, a glitch in Azure can cause a virtual machine to fail when it's manually configured to use a specific DNS server. Here's how the problem went down and how he fixed it.

If you want to convert a physical server to a Hyper-V VM, follow the steps mentioned in this guide. Do keep in mind that this physical server doesn’t have to be a server; it can be any computer, be it ...