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/dns/dns-private-resolver-get-started-portal.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ ms.custom: mode-ui
15
15
16
16
This quickstart walks you through the steps to create an Azure DNS Private Resolver (Public Preview) using the Azure portal. If you prefer, you can complete this quickstart using [Azure PowerShell](private-dns-getstarted-powershell.md).
17
17
18
-
Azure DNS Private Resolver enables you to query Azure DNS private zones from an on-premises environment, and vice versa, without deploying VM based DNS servers. You no longer need to provision IaaS based solutions on your virtual networks to resolve names registered on Azure private DNS zones. You can configure conditional forwarding of domains back to on-premises, multi-cloud and public DNS servers. For more information, including benefits, capabilities, and regional availability, see [What is Azure DNS Private Resolver](dns-private-resolver-overview.md).
18
+
Azure DNS Private Resolver enables you to query Azure DNS private zones from an on-premises environment, and vice versa, without deploying VM based DNS servers. You no longer need to provision IaaS based solutions on your virtual networks to resolve names registered on Azure private DNS zones. You can configure conditional forwarding of domains back to on-premises, multicloud and public DNS servers. For more information, including benefits, capabilities, and regional availability, see [What is Azure DNS Private Resolver](dns-private-resolver-overview.md).
Copy file name to clipboardExpand all lines: articles/dns/dns-private-resolver-overview.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ ms.custom: references_regions
6
6
author: greg-lindsay
7
7
ms.service: dns
8
8
ms.topic: overview
9
-
ms.date: 08/02/2022
9
+
ms.date: 08/17/2022
10
10
ms.author: greglin
11
11
#Customer intent: As an administrator, I want to evaluate Azure DNS Private Resolver so I can determine if I want to use it instead of my current DNS resolver service.
12
12
---
@@ -38,7 +38,7 @@ The DNS query process when using an Azure DNS Private Resolver is summarized bel
38
38
39
39
The architecture for Azure DNS Private Resolver is summarized in the following figure. DNS resolution between Azure virtual networks and on-premises networks requires [Azure ExpressRoute](../expressroute/expressroute-introduction.md) or a [VPN](../vpn-gateway/vpn-gateway-about-vpngateways.md).
40
40
41
-
[](./media/dns-resolver-overview/resolver-architecture.png#lightbox)
41
+
[](./media/dns-resolver-overview/resolver-architecture-highres.png#lightbox)
42
42
43
43
Figure 1: Azure DNS Private Resolver architecture
44
44
@@ -112,7 +112,7 @@ The following restrictions hold with respect to virtual networks:
112
112
Subnets used for DNS resolver have the following limitations:
113
113
- A subnet must be a minimum of /28 address space or a maximum of /24 address space.
114
114
- A subnet can't be shared between multiple DNS resolver endpoints. A single subnet can only be used by a single DNS resolver endpoint.
115
-
- All IP configurations for a DNS resolver inbound endpoint must reference the same subnet. Spanning multiple subnets in the IP configuration for a single DNS resolver inbound endpoint is not allowed.
115
+
- All IP configurations for a DNS resolver inbound endpoint must reference the same subnet. Spanning multiple subnets in the IP configuration for a single DNS resolver inbound endpoint isn't allowed.
116
116
- The subnet used for a DNS resolver inbound endpoint must be within the virtual network referenced by the parent DNS resolver.
117
117
118
118
### Outbound endpoint restrictions
@@ -133,5 +133,9 @@ Outbound endpoints have the following limitations:
133
133
## Next steps
134
134
135
135
* Learn how to create an Azure DNS Private Resolver by using [Azure PowerShell](./dns-private-resolver-get-started-powershell.md) or [Azure portal](./dns-private-resolver-get-started-portal.md).
136
+
* Understand how to [Resolve Azure and on-premises domains](private-resolver-hybrid-dns.md) using the Azure DNS Private Resolver.
137
+
* Learn about [Azure DNS Private Resolver endpoints and rulesets](private-resolver-endpoints-rulesets.md).
138
+
* Learn how to [Set up DNS failover using private resolvers](tutorial-dns-private-resolver-failover.md)
139
+
* Learn how to [configure hybrid DNS](private-resolver-hybrid-dns.md) using private resolvers.
136
140
* Learn about some of the other key [networking capabilities](../networking/fundamentals/networking-overview.md) of Azure.
137
141
*[Learn module: Introduction to Azure DNS](/learn/modules/intro-to-azure-dns).
0 commit comments