If you are planning to deploy Domain Controllers in Microsoft Azure, the first step will be the DNS Server configuration pointing out to the local Domain Controllers and after building the first Domain Controller in the Cloud, then you probably want to change the DNS Settings of your local network to point out to the Domain Controllers that are close to the VMs in Azure.
Let’s start with an ipconfig of a server located in the Microsoft Azure, and that server was the first Domain Controller that we prometed on the Azure side. At this point, the primary is an IP address located on-premises (10.60.99.50).
Changing the DNS Server configuration…
Logged on the Azure Portal, click on Networks, and then on DNS Servers.
Click on New, Network Services, Virtual Network, Register DNS Server and add the name and the IP address of the Domain Controller in Microsoft Azure side. Click on Register DNS Server to add the new information.
Wait for the message saying that the entry was added successfully.
Now we can see that we have two DNS Server entries available for the networks, however, that does not mean that the current servers will receive that new information.
Updating the existent Virtual Network…
In order to specify the DNS Server of any given Virtual Network, we need to click on Configure inside of the Virtual Network properties, and then remove the current primary one and select the new entry (the Azure DNS), and then add a secondary and tertiary DNS Server settings. The order is important because the order being displayed there will be the one used by the VMs. To confirm the changes hit save.
Now, we just need to schedule a restart of the VM and after the restart we can run the ipconfig again and we will see the changes in production, as shown in the figure below.
In this Tutorial we went over the process to add a new DNS Server and how to configure the new entry at the Virtual Network level.