QuestionQ48

VerifiedImplementación y administración de una infraestructura de red local e híbrida

Your on-premises network contains an Active Directory Domain Services (AD DS) domain named fabrikam.com. The domain includes a domain controller named DC1. DC1 has the DNS Server role installed and hosts the DNS primary zone for fabrikam.com.

You have an Azure subscription that contains a virtual network named VNet1. VNet1 includes a virtual machine named VM1.

The on-premises network is connected to Azure by using a Site-to-Site (S2S) VPN.

From the Azure Command-Line interface (CLI), you run the following commands.

New-AzPrivateDnsZone -Name azure.fabrikam.com -ResourceGroupName RG1  
  
New-AzPrivateDnsVirtualNetworkLink -ZoneName "azure.fabrikam.com" -ResourceGroupName "RG1" -Name "DNSlink" -VirtualNetworkId $VNET1.id  

For each of the following statements, select Yes if the statement is true. Otherwise, select No.

Yes or No
StatementsYesNo
Adding a zone delegation to fabrikam.com will enable on-premises hosts to resolve records in azure.fabrikam.com.
Adding a conditional forwarder to DC1 will enable on-premises hosts to resolve records in azure.fabrikam.com.
VM1 will be registered in azure.fabrikam.com automatically.
Explanation

An Azure private DNS zone is not exposed as a delegable authoritative DNS zone for on-premises DNS servers. Hybrid resolution requires an Azure DNS Private Resolver inbound endpoint or a DNS forwarder in an Azure virtual network; a conditional forwarder on DC1 alone cannot resolve the private zone. Automatic VM record registration requires the virtual-network link to be created with -EnableRegistration, which is absent.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!