Skip to content

Commit cfaea52

Browse files
authored
Merge pull request #275791 from greg-lindsay/dns-azdns
azdns define
2 parents 9a099d5 + 4dfce5e commit cfaea52

File tree

5 files changed

+107
-63
lines changed

5 files changed

+107
-63
lines changed

articles/dns/TOC.yml

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,16 @@
22
href: index.yml
33
- name: Overview
44
items:
5-
- name: What is Azure DNS?
5+
- name: Azure DNS overview
66
href: dns-overview.md
7+
- name: What is Azure Public DNS?
8+
href: public-dns-overview.md
79
- name: What is Azure Private DNS?
810
href: private-dns-overview.md
911
- name: What is Azure DNS Private Resolver?
1012
href: dns-private-resolver-overview.md
13+
- name: What is Azure Traffic Manager?
14+
href: /azure/traffic-manager/traffic-manager-overview
1115
- name: Quickstarts
1216
items:
1317
- name: Public DNS

articles/dns/dns-overview.md

Lines changed: 31 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -1,70 +1,49 @@
11
---
2-
title: What is Azure DNS?
3-
description: Overview of DNS hosting service on Microsoft Azure. Host your domain on Microsoft Azure.
2+
title: Azure DNS overview
3+
description: An overview of services provided by Azure DNS.
44
author: greg-lindsay
55
ms.service: azure-dns
66
ms.topic: overview
7-
ms.date: 11/30/2023
7+
ms.date: 08/12/2024
88
ms.author: greglin
99
#Customer intent: As an administrator, I want to evaluate Azure DNS so I can determine if I want to use it instead of my current DNS service.
1010
---
1111

12-
# What is Azure DNS?
12+
# Azure DNS overview
1313

14-
Azure DNS is a hosting service for DNS domains that provides name resolution by using Microsoft Azure infrastructure. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools, and billing as your other Azure services.
14+
The Domain Name System (DNS) is responsible for translating (resolving) a service name to an IP address. Azure DNS provides DNS hosting, resolution, and load balancing for your applications using the Microsoft Azure infrastructure.
1515

16-
You can't use Azure DNS to buy a domain name. For an annual fee, you can buy a domain name by using [App Service domains](../app-service/manage-custom-dns-buy-domain.md#buy-and-map-an-app-service-domain) or a third-party domain name registrar. Your domains then can be hosted in Azure DNS for record management. For more information, see [Delegate a domain to Azure DNS](dns-domain-delegation.md).
16+
Azure DNS supports both internet-facing DNS domains and private DNS zones, and provides the following services:
17+
- **[Azure Public DNS](public-dns-overview.md)** is a hosting service for DNS domains. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools, and billing as your other Azure services.
1718

18-
The following features are included with Azure DNS.
19+
- **[Azure Private DNS](private-dns-overview.md)** is a DNS service for your virtual networks. Azure Private DNS manages and resolves domain names in the virtual network without the need to configure a custom DNS solution.
1920

20-
## Reliability and performance
21+
- **[Azure DNS Private Resolver](dns-private-resolver-overview.md)** is a service that enables you to query Azure DNS private zones from an on-premises environment and vice versa without deploying VM based DNS servers.
2122

22-
DNS domains in Azure DNS are hosted on Azure's global network of DNS name servers. Azure DNS uses anycast networking. Each DNS query is answered by the closest available DNS server to provide fast performance and high availability for your domain.
23+
- **[Azure Traffic Manager](/azure/traffic-manager/traffic-manager-overview)** is a DNS-based traffic load balancer. This service allows you to distribute traffic to your public facing applications across the global Azure regions.
2324

24-
## Security
25+
Azure DNS enables multiple scenarios, including:
2526

26-
Azure DNS is based on Azure Resource Manager, which provides features such as:
27-
28-
* [Azure role-based access control (Azure RBAC)](../azure-resource-manager/management/overview.md) to control who has access to specific actions for your organization.
29-
30-
* [Activity logs](../azure-resource-manager/management/overview.md) to monitor how a user in your organization modified a resource or to find an error when troubleshooting.
31-
32-
* [Resource locking](../azure-resource-manager/management/lock-resources.md) to lock a subscription, resource group, or resource. Locking prevents other users in your organization from accidentally deleting or modifying critical resources.
33-
34-
For more information, see [How to protect DNS zones and records](dns-protect-zones-recordsets.md).
35-
36-
## DNSSEC
37-
38-
Azure DNS does not currently support DNSSEC. In most cases, you can reduce the need for DNSSEC by consistently using HTTPS/TLS in your applications. If DNSSEC is a critical requirement for your DNS zones, you can host these zones with third-party DNS hosting providers.
39-
40-
## Ease of use
41-
42-
Azure DNS can manage DNS records for your Azure services and provide DNS for your external resources as well. Azure DNS is integrated in the Azure portal and uses the same credentials, support contract, and billing as your other Azure services.
43-
44-
DNS billing is based on the number of DNS zones hosted in Azure and on the number of DNS queries received. To learn more about pricing, see [Azure DNS pricing](https://azure.microsoft.com/pricing/details/dns/).
45-
46-
Your domains and records can be managed by using the Azure portal, Azure PowerShell cmdlets, and the cross-platform Azure CLI. Applications that require automated DNS management can integrate with the service by using the REST API and SDKs.
47-
48-
## Customizable virtual networks with private domains
49-
50-
Azure DNS also supports private DNS domains. This feature allows you to use your own custom domain names in your private virtual networks rather than the Azure-provided names available today.
51-
52-
For more information, see [Use Azure DNS for private domains](private-dns-overview.md).
53-
54-
## Alias records
55-
56-
Azure DNS supports alias record sets. You can use an alias record set to refer to an Azure resource, such as an Azure public IP address, an Azure Traffic Manager profile, or an Azure Content Delivery Network (CDN) endpoint. If the IP address of the underlying resource changes, the alias record set seamlessly updates itself during DNS resolution. The alias record set points to the service instance, and the service instance is associated with an IP address.
57-
58-
Also, you can now point your apex or naked domain to a Traffic Manager profile or CDN endpoint using an alias record. An example is contoso.com.
59-
60-
For more information, see [Overview of Azure DNS alias records](dns-alias.md).
27+
* [Host and resolve public domains](/azure/dns/dns-delegate-domain-azure-dns)
28+
* [Manage DNS resolution in your virtual networks](/azure/dns/private-dns-privatednszone)
29+
* [Enable autoregistration for VMs](/azure/dns/private-dns-autoregistration)
30+
* [Enable name resolution between Azure and your on-premises resources](/azure/dns/private-resolver-hybrid-dns)
31+
* [Secure hybrid networking](/azure/architecture/networking/architecture/azure-dns-private-resolver#use-dns-private-resolver)
32+
* [Monitor DNS metrics and alerts](/azure/dns/dns-alerts-metrics)
33+
* [Integrate with your other Azure services](/azure/dns/dns-for-azure-services)
34+
* [Perform Private Link and DNS integration at scale](/azure/cloud-adoption-framework/ready/azure-best-practices/private-link-and-dns-integration-at-scale)
35+
* Protect your [public](/azure/dns/dns-protect-zones-recordsets) and [private](/azure/dns/dns-protect-private-zones-recordsets) DNS zones and records
36+
* Enable automatic [fault tolerance](/azure/dns/private-resolver-reliability) and [failover](/azure/dns/tutorial-dns-private-resolver-failover) for DNS resolution
37+
* [Load-balance your applications](/azure/traffic-manager/traffic-manager-how-it-works)
38+
* Increase application [availability](/azure/traffic-manager/traffic-manager-monitoring) and [performance](/azure/traffic-manager/traffic-manager-configure-performance-routing-method)
39+
* [Monitor your application traffic patterns](/azure/traffic-manager/traffic-manager-traffic-view-overview)
6140

6241
## Next steps
6342

64-
* To learn about DNS zones and records, see [DNS zones and records overview](dns-zones-records.md).
65-
66-
* To learn how to create a zone in Azure DNS, see [Create a DNS zone](./dns-getstarted-portal.md).
67-
68-
* For frequently asked questions about Azure DNS, see the [Azure DNS FAQ](dns-faq.yml).
69-
70-
* [Learn module: Introduction to Azure DNS](/training/modules/intro-to-azure-dns).
43+
* To learn about Public DNS zones and records, see [DNS zones and records overview](dns-zones-records.md).
44+
* To learn about Private DNS zones, see [What is an Azure Private DNS zone](private-dns-privatednszone.md).
45+
* To learn about private resolver endpoints and rulesets, see [Azure DNS Private Resolver endpoints and rulesets](private-resolver-endpoints-rulesets.md).
46+
* For frequently asked questions about Azure DNS, see [Azure DNS FAQ](dns-faq-private.yml).
47+
* For frequently asked questions about Azure Private DNS, see [Azure Private DNS FAQ](dns-faq.yml).
48+
* For frequently asked questions about Traffic Manager, see [Traffic Manager routing methods](/azure/traffic-manager/traffic-manager-faqs)
49+
* Also see [Learn module: Introduction to Azure DNS](/training/modules/intro-to-azure-dns).

articles/dns/dns-private-resolver-overview.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
---
22
title: What is Azure DNS Private Resolver?
33
description: In this article, get started with an overview of the Azure DNS Private Resolver service.
4-
services: dns
54
ms.custom: references_regions
65
author: greg-lindsay
76
ms.service: azure-dns
87
ms.topic: overview
9-
ms.date: 07/01/2024
8+
ms.date: 08/09/2024
109
ms.author: greglin
1110
#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.
1211
---
@@ -17,7 +16,7 @@ Azure DNS Private Resolver is a new service that enables you to query Azure DNS
1716

1817
## How does it work?
1918

20-
Azure DNS Private Resolver requires an [Azure Virtual Network](../virtual-network/virtual-networks-overview.md). When you create an Azure DNS Private Resolver inside a virtual network, one or more [inbound endpoints](#inbound-endpoints) are established that can be used as the destination for DNS queries. The resolver's [outbound endpoint](#outbound-endpoints) processes DNS queries based on a [DNS forwarding ruleset](#dns-forwarding-rulesets) that you configure. DNS queries that are initiated in networks linked to a ruleset can be sent to other DNS servers.
19+
Azure DNS Private Resolver requires an [Azure Virtual Network](../virtual-network/virtual-networks-overview.md). When you create an Azure DNS Private Resolver inside a virtual network, one or more [inbound endpoints](#inbound-endpoints) are established that can be used as the destination for DNS queries. The resolver's [outbound endpoint](#outbound-endpoints) processes DNS queries based on a [DNS forwarding ruleset](#dns-forwarding-rulesets) that you configure. DNS queries that are initiated in networks linked to a ruleset can be sent to other DNS servers.
2120

2221
You don't need to change any DNS client settings on your virtual machines (VMs) to use the Azure DNS Private Resolver.
2322

@@ -101,7 +100,7 @@ The following limits currently apply to Azure DNS Private Resolver:
101100
### Virtual network restrictions
102101

103102
The following restrictions hold with respect to virtual networks:
104-
- VNets with [encryption](/azure/virtual-network/virtual-network-encryption-overview) enabled do not support Azure DNS Private Resolver.
103+
- VNets with [encryption](/azure/virtual-network/virtual-network-encryption-overview) enabled don't support Azure DNS Private Resolver.
105104
- A DNS resolver can only reference a virtual network in the same region as the DNS resolver.
106105
- A virtual network can't be shared between multiple DNS resolvers. A single virtual network can only be referenced by a single DNS resolver.
107106

@@ -126,7 +125,7 @@ Outbound endpoints have the following limitations:
126125
### Other restrictions
127126

128127
- IPv6 enabled subnets aren't supported.
129-
- DNS private resolver does not support Azure ExpressRoute FastPath.
128+
- DNS private resolver doesn't support Azure ExpressRoute FastPath.
130129
- DNS private resolver inbound endpoint provisioning isn't compatible with [Azure Lighthouse](../lighthouse/overview.md).
131130
- To see if Azure Lighthouse is in use, search for **Service providers** in the Azure portal and select **Service provider offers**.
132131

articles/dns/private-dns-overview.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,27 +1,24 @@
11
---
22
title: What is Azure Private DNS?
33
description: In this article, get started with an overview of the private DNS hosting service on Microsoft Azure.
4-
services: dns
54
author: greg-lindsay
65
ms.service: azure-dns
76
ms.topic: overview
8-
ms.date: 06/21/2024
7+
ms.date: 08/09/2024
98
ms.author: greglin
109
#Customer intent: As an administrator, I want to evaluate Azure Private DNS so I can determine if I want to use it instead of my current DNS service.
1110
---
1211

1312
# What is Azure Private DNS?
1413

15-
The Domain Name System (DNS) is responsible for translating (resolving) a service name to an IP address. Azure DNS is a hosting service for domains and provides naming resolution using the Microsoft Azure infrastructure. Azure DNS not only supports internet-facing DNS domains, but it also supports private DNS zones.
16-
1714
Azure Private DNS provides a reliable and secure DNS service for your virtual networks. Azure Private DNS manages and resolves domain names in the virtual network without the need to configure a custom DNS solution. By using private DNS zones, you can use your own custom domain name instead of the Azure-provided names during deployment. Using a custom domain name helps you tailor your virtual network architecture to best suit your organization's needs. It provides a naming resolution for virtual machines (VMs) within a virtual network and connected virtual networks. Additionally, you can configure zones names with a split-horizon view, which allows a private and a public DNS zone to share the name.
1815

1916
To resolve the records of a private DNS zone from your virtual network, you must link the virtual network with the zone. Linked virtual networks have full access and can resolve all DNS records published in the private zone. You can also enable [autoregistration](private-dns-autoregistration.md) on a [virtual network link](private-dns-virtual-network-links.md). When you enable autoregistration on a virtual network link, the DNS records for the virtual machines in that virtual network are registered in the private zone. When autoregistration gets enabled, Azure DNS will update the zone record whenever a virtual machine gets created, changes its' IP address, or gets deleted.
2017

2118
![DNS overview](./media/private-dns-overview/scenario.png)
2219

2320
> [!NOTE]
24-
> As a best practice, do not use a *.local* domain for your private DNS zone. Not all operating systems support this.
21+
> As a best practice, don't use a *.local* domain for your private DNS zone. Not all operating systems support this.
2522
2623
## Private zone resiliency
2724

articles/dns/public-dns-overview.md

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: What is Azure Public DNS?
3+
description: Overview of DNS hosting service on Microsoft Azure. Host your domain on Microsoft Azure.
4+
author: greg-lindsay
5+
ms.service: azure-dns
6+
ms.topic: overview
7+
ms.date: 08/09/2024
8+
ms.author: greglin
9+
#Customer intent: As an administrator, I want to evaluate Azure Public DNS so I can determine if I want to use it instead of my current DNS service.
10+
---
11+
12+
# What is Azure Public DNS?
13+
14+
Azure Public DNS is a hosting service for DNS domains that provides name resolution by using Microsoft Azure infrastructure. By hosting your domains in Azure, you can manage your DNS records by using the same credentials, APIs, tools, and billing as your other Azure services.
15+
16+
You can't use Azure Public DNS to buy a domain name. For an annual fee, you can buy a domain name by using [App Service domains](../app-service/manage-custom-dns-buy-domain.md#buy-and-map-an-app-service-domain) or a third-party domain name registrar. Your domains then can be hosted in Azure Public DNS for record management. For more information, see [Delegate a domain to Azure DNS](dns-domain-delegation.md).
17+
18+
The following features are included with Azure Public DNS.
19+
20+
## Reliability and performance
21+
22+
DNS domains in Azure Public DNS are hosted on Azure's global network of DNS name servers. Azure Public DNS uses anycast networking. Each DNS query is answered by the closest available DNS server to provide fast performance and high availability for your domain.
23+
24+
## Security
25+
26+
Azure Public DNS is based on Azure Resource Manager, which provides features such as:
27+
28+
* [Azure role-based access control (Azure RBAC)](../azure-resource-manager/management/overview.md) to control who has access to specific actions for your organization.
29+
* [Activity logs](../azure-resource-manager/management/overview.md) to monitor how a user in your organization modified a resource or to find an error when troubleshooting.
30+
* [Resource locking](../azure-resource-manager/management/lock-resources.md) to lock a subscription, resource group, or resource. Locking prevents other users in your organization from accidentally deleting or modifying critical resources.
31+
32+
For more information, see [How to protect DNS zones and records](dns-protect-zones-recordsets.md).
33+
34+
## DNSSEC
35+
36+
Azure Public DNS doesn't currently support DNSSEC. In most cases, you can reduce the need for DNSSEC by consistently using HTTPS/TLS in your applications. If DNSSEC is a critical requirement for your DNS zones, you can host these zones with third-party DNS hosting providers.
37+
38+
## Ease of use
39+
40+
Azure Public DNS can manage DNS records for your Azure services and provide DNS for your external resources as well. Azure Public DNS is integrated in the Azure portal and uses the same credentials, support contract, and billing as your other Azure services.
41+
42+
DNS billing is based on the number of DNS zones hosted in Azure and on the number of DNS queries received. To learn more about pricing, see [Azure DNS pricing](https://azure.microsoft.com/pricing/details/dns/).
43+
44+
Your domains and records can be managed by using the Azure portal, Azure PowerShell cmdlets, and the cross-platform Azure CLI. Applications that require automated DNS management can integrate with the service by using the REST API and SDKs.
45+
46+
## Customizable virtual networks with private domains
47+
48+
Azure Public DNS also supports private DNS domains. This feature allows you to use your own custom domain names in your private virtual networks rather than the Azure-provided names available today.
49+
50+
For more information, see [Use Azure DNS for private domains](private-dns-overview.md).
51+
52+
## Alias records
53+
54+
Azure Public DNS supports alias record sets. You can use an alias record set to refer to an Azure resource, such as an Azure public IP address, an Azure Traffic Manager profile, or an Azure Content Delivery Network (CDN) endpoint. If the IP address of the underlying resource changes, the alias record set seamlessly updates itself during DNS resolution. The alias record set points to the service instance, and the service instance is associated with an IP address.
55+
56+
Also, you can now point your apex or naked domain to a Traffic Manager profile or CDN endpoint using an alias record. An example is contoso.com.
57+
58+
For more information, see [Overview of Azure DNS alias records](dns-alias.md).
59+
60+
## Next steps
61+
62+
* To learn about DNS zones and records, see [DNS zones and records overview](dns-zones-records.md).
63+
* To learn how to create a zone in Azure Public DNS, see [Create a DNS zone](./dns-getstarted-portal.md).
64+
* For frequently asked questions about Azure DNS, see the [Azure DNS FAQ](dns-faq.yml).
65+
* [Learn module: Introduction to Azure DNS](/training/modules/intro-to-azure-dns).

0 commit comments

Comments
 (0)