You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-domain-services/manage-dns.md
+37-10Lines changed: 37 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Manage DNS for Azure AD Domain Services | Microsoft Docs
3
-
description: Learn how to install the DNS Server Tools to manage DNS for an Azure Active Directory Domain Services managed domain.
3
+
description: Learn how to install the DNS Server Tools to manage DNS and create conditional forwarders for an Azure Active Directory Domain Services managed domain.
4
4
author: iainfoulds
5
5
manager: daveba
6
6
@@ -9,21 +9,19 @@ ms.service: active-directory
9
9
ms.subservice: domain-services
10
10
ms.workload: identity
11
11
ms.topic: how-to
12
-
ms.date: 10/31/2019
12
+
ms.date: 04/16/2020
13
13
ms.author: iainfou
14
14
15
15
---
16
-
# Administer DNS in an Azure AD Domain Services managed domain
16
+
# Administer DNS and create conditional forwarders in an Azure AD Domain Services managed domain
17
17
18
18
In Azure Active Directory Domain Services (Azure AD DS), a key component is DNS (Domain Name Resolution). Azure AD DS includes a 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.
19
19
20
20
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.
21
21
22
-
In a hybrid environment, DNS zones and records configured in an on-premises AD DS environment aren't synchronized to Azure AD DS. To define and use your own DNS entries, create records in the Azure AD DS DNS server or use conditional forwarders that point to existing DNS servers in your environment.
22
+
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 Azure AD DS. To resolve named resources in other DNS namespaces, create and use conditional forwarders that point to existing DNS servers in your environment.
23
23
24
-
This article shows you how to install the DNS Server tools then use the DNS console to manage records in Azure AD DS.
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.
27
25
28
26
## Before you begin
29
27
@@ -35,6 +33,8 @@ To complete this article, you need the following resources and privileges:
35
33
* If needed, [create an Azure Active Directory tenant][create-azure-ad-tenant] or [associate an Azure subscription with your account][associate-azure-ad-tenant].
36
34
* An Azure Active Directory Domain Services managed domain enabled and configured in your Azure AD tenant.
37
35
* If needed, complete the tutorial to [create and configure an Azure Active Directory Domain Services instance][create-azure-ad-ds-instance].
36
+
* Connectivity from your Azure AD DS virtual network to where your other DNS namespaces are hosted.
37
+
* This connectivity can be provided with an [Azure ExpressRoute][expressroute] or [Azure VPN Gateway][vpn-gateway] connection.
38
38
* A Windows Server management VM that is joined to the Azure AD DS managed domain.
39
39
* If needed, complete the tutorial to [create a Windows Server VM and join it to a managed domain][create-join-windows-vm].
40
40
* A user account that's a member of the *Azure AD DC administrators* group in your Azure AD tenant.
@@ -52,7 +52,7 @@ To create and modify DNS records in Azure AD DS, you need to install the DNS Ser
52
52
1. On the **Server Roles** page, click **Next**.
53
53
1. 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.
54
54
55
-

55
+

56
56
57
57
1. On the **Confirmation** page, select **Install**. It may take a minute or two to install the Group Policy Management tools.
58
58
1. When feature installation is complete, select **Close** to exit the **Add Roles and Features** wizard.
@@ -67,15 +67,40 @@ With the DNS Server tools installed, you can administer DNS records on the Azure
67
67
1. 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.
68
68
1. 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*:
69
69
70
-

70
+

71
71
72
72
1. The DNS Console connects to the specified Azure AD DS managed domain. Expand the **Forward Lookup Zones** or **Reverse Lookup Zones** to create your required DNS entries or edit existing records as needed.
73
73
74
-

74
+

75
75
76
76
> [!WARNING]
77
77
> 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.
78
78
79
+
## Create conditional forwarders
80
+
81
+
An Azure AD DS DNS zone should only contain the zone and records for the managed domain itself. Don't create additional zones in Azure AD DS to resolve named resources in other DNS namespaces. Instead, use conditional forwarders in the Azure AD DS managed domain to tell the DNS server where to go in order to resolve addresses for those resources.
82
+
83
+
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 Azure AD DS managed domain to reflect those resources.
84
+
85
+
To create a conditional forwarder in your Azure AD DS managed domain, complete the following steps:
86
+
87
+
1. Select your Azure AD DS DNS zone, such as *aaddscontoso.com*.vb
88
+
1. Select **Conditional Forwarders**, then right-select and choose **New Conditional Forwarder...**
89
+
1. 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:
90
+
91
+

92
+
93
+
1. 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:
94
+
95
+

96
+
97
+
> [!IMPORTANT]
98
+
> If the conditional forwarder is stored in the *forest* instead of the *domain*, the conditional forwarder fails.
99
+
100
+
1. To create the conditional forwarder, select **OK**.
101
+
102
+
Name resolution of the resources in other namespaces from VMs connected to the Azure AD DS managed domain should now resolve correctly. Queries for the DNS domain configured in the conditional forwarder are passed to the relevant DNS servers.
103
+
79
104
## Next steps
80
105
81
106
For more information about managing DNS, see the [DNS tools article on Technet](https://technet.microsoft.com/library/cc753579.aspx).
@@ -84,6 +109,8 @@ For more information about managing DNS, see the [DNS tools article on Technet](
0 commit comments