Skip to content
This repository was archived by the owner on Dec 6, 2024. It is now read-only.

Azure DNS Private resolver as an option #267

Open
Ravivarman13 wants to merge 6 commits into
base: main
Choose a base branch
from
Open

Azure DNS Private resolver as an option #267

Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
da7ebd0
Update dns-pe-concepts.md
Ravivarman13 Dec 5, 2023
f66f985
Update dns-pe-concepts.md
Ravivarman13 Dec 5, 2023
72b5768
Update dns-pe-concepts.md
Ravivarman13 Dec 8, 2023
9e851d7
Update dns-pe-scenarios.md
Ravivarman13 Dec 8, 2023
2e85993
Update dns-pe-concepts.md
Ravivarman13 Dec 10, 2023
4f2f7bb
Merge branch 'main' into main
mbrat2005 May 28, 2024
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-concepts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ A common challenge is that organizations wish to use their own zone names for th

## DNS Options in Azure

There are two primary options to consider for creating DNS records for your Private Endpoint resources:
There are three primary options to consider for creating DNS records for your Private Endpoint resources:

- **Private DNS Zones:** Private DNS Zones are Azure's native Private DNS offering and integrate with the default Azure-provided DNS service. Using Private DNS Zones with your Private Endpoints enables automated DNS record management for your Private Endpoints, improving scale and ease of management.
- **Custom DNS servers:** Custom DNS servers are when you bring your own DNS servers to Azure point your DNS clients to them. Commonly, these are Windows Domain Controllers hosting an extension of your on-prem DNS services. Custom DNS servers can be combined with Private DNS zones to provide both the consistency of your extended DNS service and the flexibility of Private DNS Zones. Alternatively, you can skip Private DNS Zones altogether and create 'A' DNS records for your Private Endpoints directly in your Custom DNS server--this is usually not recommended because it scales poorly without significant automation investment.
Expand Down
2 changes: 1 addition & 1 deletion content/networking/private-endpoints/dns-pe-scenarios.md
View file
Open in desktop
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

@mbrat2005 mbrat2005 May 28, 2024

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