Learn how to configure Azure Virtual Network (VNet) DNS settings to resolve domain names and enable domain joining for Azure VMs with minimal administrative effort. Discover the best solution for connecting to your on-premises Active Directory (AD DS) domain.
Table of Contents
Question
You have an Azure subscription that includes an Azure Virtual Network named VNet1 connected to an on-premises Active Directory Domain Services (AD DS) domain named contoso.com. Contoso.com contains a domain controller named DC1 that hosts the DNS records for the domain.
You create an Azure Virtual Machine named VM1 in VNet1.
You need to ensure that VM1 can resolve the contoso.com name and join the domain. The solution must minimize administrative effort.
What should you do?
A. Change the DNS settings of VNet1 to use a custom DNS address pointing to DC1.
B. Change the DNS settings of VM1 to use the Azure DNS server of 168.63.129.16.
C. Change the DNS settings of VNet1 to point to a public DNS server.
D. Create an Azure Private DNS zone.
Answer
A. Change the DNS settings of VNet1 to use a custom DNS address pointing to DC1.
Explanation
The default DNS for the virtual network is to use the Azure Default DNS server, which will not have the on-premises DC records.
On-premises DNS must not be visible to the Azure DNS servers. The default when creating a virtual network is for Azure to provide DNS resolution.
When a virtual machine is domain joined, DNS is queried for the appropriate records advertising the domain controller.
Designing and Implementing Microsoft Azure Networking Solutions AZ-700 certification exam assessment practice question and answer (Q&A) dump including multiple choice questions (MCQ) and objective type questions, with detail explanation and reference available free, helpful to pass the Designing and Implementing Microsoft Azure Networking Solutions AZ-700 exam and earn Designing and Implementing Microsoft Azure Networking Solutions AZ-700 certification.