Skip to content
This repository was archived by the owner on Dec 6, 2024. It is now read-only.
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/networking/private-endpoints/dns-pe-scenarios.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ In this scenario...

It should be noted that these DNS forwarders can be many different kinds of resources, such as:

- Azure Private DNS Resolvers
- Azure Private DNS Resolvers : It is a fully managed service that enables you to query Azure Private DNS Zones from an on-premises environment and vice versa without deploying custom DNS servers in Azure. Azure DNS Private Resolver requires an Azure Virtual Network.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Azure Private DNS Resolvers : It is a fully managed service that enables you to query Azure Private DNS Zones from an on-premises environment and vice versa without deploying custom DNS servers in Azure. Azure DNS Private Resolver requires an Azure Virtual Network.
- Azure Private DNS Resolver : A fully managed service that enables you to query Azure Private DNS Zones from an on-premises environment and vice versa without deploying custom DNS servers in Azure. Azure DNS Private Resolver requires an Azure Virtual Network.

- Windows Server DNS Server or AD Domain Controller
- A third party DNS solution

Expand Down