Administer DNS and create conditional forwarders in an Azure Active Directory Domain Services managed domain
Azure AD DS includes a Domain Name System (DNS) server that provides name resolution for the managed domain. This DNS server includes built-in DNS records and updates for the key components that allow the service to run.
As you run your own applications and services, you may need to create DNS records for machines that aren't joined to the domain, configure virtual IP addresses for load balancers, or set up external DNS forwarders. Users who belong to the AAD DC Administrators group are granted DNS administration privileges on the Azure AD DS managed domain and can create and edit custom DNS records.
In a hybrid environment, DNS zones and records configured in other DNS namespaces, such as an on-premises AD DS environment, aren't synchronized to the managed domain. To resolve named resources in other DNS namespaces, create and use conditional forwarders that point to existing DNS servers in your environment.
This article shows you how to install the DNS Server tools then use the DNS console to manage records and create conditional forwarders in Azure AD DS.
Creating or changing root hints or server-level DNS forwarders is not supported and will cause issues for the Azure AD DS managed domain.
Before you begin
To complete this article, you need the following resources and privileges:
- An active Azure subscription.
- If you don't have an Azure subscription, create an account.
- An Azure Active Directory tenant associated with your subscription, either synchronized with an on-premises directory or a cloud-only directory.
- An Azure Active Directory Domain Services managed domain enabled and configured in your Azure AD tenant.
- If needed, complete the tutorial to create and configure an Azure Active Directory Domain Services managed domain.
- Connectivity from your Azure AD DS virtual network to where your other DNS namespaces are hosted.
- This connectivity can be provided with an Azure ExpressRoute or Azure VPN Gateway connection.
- A Windows Server management VM that is joined to the managed domain.
- If needed, complete the tutorial to create a Windows Server VM and join it to a managed domain.
- A user account that's a member of the Azure AD DC administrators group in your Azure AD tenant.
Install DNS Server tools
To create and modify DNS records in a managed domain, you need to install the DNS Server tools. These tools can be installed as a feature in Windows Server. For more information on how to install the administrative tools on a Windows client, see install Remote Server Administration Tools (RSAT).
Sign in to your management VM. For steps on how to connect using the Azure portal, see Connect to a Windows Server VM.
If Server Manager doesn't open by default when you sign in to the VM, select the Start menu, then choose Server Manager.
In the Dashboard pane of the Server Manager window, select Add Roles and Features.
On the Before You Begin page of the Add Roles and Features Wizard, select Next.
For the Installation Type, leave the Role-based or feature-based installation option checked and select Next.
On the Server Selection page, choose the current VM from the server pool, such as myvm.aaddscontoso.com, then select Next.
On the Server Roles page, click Next.
On the Features page, expand the Remote Server Administration Tools node, then expand the Role Administration Tools node. Select DNS Server Tools feature from the list of role administration tools.
On the Confirmation page, select Install. It may take a minute or two to install the DNS Server Tools.
When feature installation is complete, select Close to exit the Add Roles and Features wizard.
Open the DNS management console to administer DNS
With the DNS Server tools installed, you can administer DNS records on the managed domain.
To administer DNS in a managed domain, you must be signed in to a user account that's a member of the AAD DC Administrators group.
From the Start screen, select Administrative Tools. A list of available management tools is shown, including DNS installed in the previous section. Select DNS to launch the DNS Management console.
In the Connect to DNS Server dialog, select The following computer, then enter the DNS domain name of the managed domain, such as aaddscontoso.com:
The DNS Console connects to the specified managed domain. Expand the Forward Lookup Zones or Reverse Lookup Zones to create your required DNS entries or edit existing records as needed.
When you manage records using the DNS Server tools, make sure that you don't delete or modify the built-in DNS records that are used by Azure AD DS. Built-in DNS records include domain DNS records, name server records, and other records used for DC location. If you modify these records, domain services are disrupted on the virtual network.
Create conditional forwarders
An Azure AD DS DNS zone should only contain the zone and records for the managed domain itself. Don't create additional zones in the managed domain to resolve named resources in other DNS namespaces. Instead, use conditional forwarders in the managed domain to tell the DNS server where to go in order to resolve addresses for those resources.
A conditional forwarder is a configuration option in a DNS server that lets you define a DNS domain, such as contoso.com, to forward queries to. Instead of the local DNS server trying to resolve queries for records in that domain, DNS queries are forwarded to the configured DNS for that domain. This configuration makes sure that the correct DNS records are returned, as you don't create a local a DNS zone with duplicate records in the managed domain to reflect those resources.
To create a conditional forwarder in your managed domain, complete the following steps:
Select your DNS zone, such as aaddscontoso.com.
Select Conditional Forwarders, then right-select and choose New Conditional Forwarder...
Enter your other DNS Domain, such as contoso.com, then enter the IP addresses of the DNS servers for that namespace, as shown in the following example:
Check the box for Store this conditional forwarder in Active Directory, and replicate it as follows, then select the option for All DNS servers in this domain, as shown in the following example:
If the conditional forwarder is stored in the forest instead of the domain, the conditional forwarder fails.
To create the conditional forwarder, select OK.
Name resolution of the resources in other namespaces from VMs connected to the managed domain should now resolve correctly. Queries for the DNS domain configured in the conditional forwarder are passed to the relevant DNS servers.
For more information about managing DNS, see the DNS tools article on Technet.
Submit and view feedback for