Saying Azure DNS Personal Resolver common availability | Azure Weblog and Updates

Saying Azure DNS Personal Resolver common availability | Azure Weblog and Updates

A profitable hybrid networking technique calls for DNS companies that work seamlessly throughout on-premises and cloud networks. Azure DNS Personal Resolver now offers a totally managed recursive decision and conditional forwarding service for Azure digital networks. Utilizing this service, it is possible for you to to resolve DNS names hosted in Azure DNS non-public zones from on-premises networks in addition to DNS queries originating from Azure digital networks that may be forwarded to a specified vacation spot server to resolve them.

This service will present a extremely accessible and resilient DNS infrastructure on Azure for a fraction of the value of working conventional IaaS VMs working DNS servers in digital networks. It is possible for you to to seamlessly combine with Personal DNS Zones and unlock key eventualities with minimal operational overhead.

We’re excited to share that Azure DNS Personal Resolver is now on the whole availability.

A fast overview of Azure DNS

A flow diagram of multi-region workloads running on Azure with DNS Private Resolver provisioned in two regional, centralized workloads.

We provide two forms of Azure DNS Zones—non-public and public—for internet hosting your non-public DNS and public DNS data. Within the previous illustration, multi-region workloads working on Azure with Azure DNS Personal Resolver are provisioned in two regional, centralized digital networks with a number of spokes peered to every centralized digital community. These digital networks have inbound and outbound endpoints provisioned. From on-premises, there are two distinct areas (East and West) and every location connects by way of Categorical Path to the centralized digital community the place Personal Resolver is provisioned. These on-premises areas have a number of native DNS servers configured to do conditional forwarding to the inbound endpoint of Personal Resolver. The native DNS servers in East have the IP deal with of the East inbound endpoint as the first DNS goal, and the West inbound endpoint as secondary. Alternatively, the native DNS servers in West have the IP deal with of the West inbound endpoint as the first DNS goal, and the East inbound endpoint as secondary. There’s a single non-public DNS zone linked to each areas and each on-premises areas can resolve names from this zone even within the occasion of a regional failure.

  • Azure Personal DNS: Azure Personal DNS offers a dependable and safe DNS service on your digital community. Azure Personal DNS manages and resolves domains within the digital community with out the necessity to configure a customized DNS resolution. By utilizing non-public DNS zones, you should use your individual customized area title as an alternative of the Azure-provided names throughout deployment.
  • Azure Public DNS: DNS domains in Azure DNS are hosted on Azure’s international community of DNS title servers. Azure DNS makes use of anycast networking. Every DNS question is answered by the closest accessible DNS server to offer quick efficiency and excessive availability on your area.

What’s being introduced in the present day?

Azure DNS Personal Resolver lets you question Azure DNS non-public zones from an on-premises setting and vice versa with out deploying digital machine-based DNS servers.

Azure DNS Personal Resolver common availability is being introduced to all clients and may have regional availability within the following areas:

  • East US
  • East US 2
  • Central US
  • South Central US
  • North Central US
  • West Central US
  • West US 3
  • Canada Central
  • Brazil South

  • West Europe
  • North Europe
  • UK South
  • France Central
  • Sweden Central
  • Switzerland North

  • East Asia
  • Southeast Asia
  • Japan East
  • Korea Central
  • South Africa North
  • Australia East


What is going to clients have the ability to do with Azure Personal Resolver?

Other than the options which had been introduced earlier in preview, clients will now have the ability to leverage the next extra performance and content material:

Within the following diagram, an on-premises community connects to Azure by way of ExpressRoute and has on-premises DNS servers configured to conditionally ahead queries to the non-public IP deal with of the inbound endpoint. The inbound endpoint then resolves names accessible on Azure Personal DNS zones that are linked to the digital community the place non-public resolver is provisioned. If there isn’t any matching non-public DNS zone within the digital community, it can use the outbound endpoint and resolve utilizing the ruleset guidelines by way of longest suffix match. If no match within the ruleset is discovered it can recurse to the web for public title decision.

A diagram showing an on-premises network connected to Azure via ExpressRoute forwarding queries to the private IP address of the inbound endpoint. The inbound endpoint then resolves names available on Azure Private DNS zones.

Options and advantages

  • Cross-subscription assist to hyperlink digital networks from totally different subscriptions to rulesets.
  • Useful resource Well being Verify Integration to offer visibility of endpoint well being to our clients.

Alert condition for resource health check can be configured in the Portal and allows to select resource status on which you’d like to receive alerts such as: available, degraded, and unavailable.


  • Visibility of question metrics per endpoint to plan for future capability:

Query metrics per endpoint are shown in a bar graph.

  • PrivateLink enabled companies integration in conditional forwarding to exclude Azure infra zones from being resolved on-premises.

Personal Resolver common availability can also be accessible to make use of by way of PowerShell, CLI, .NET, Java, Python, REST, Typescript, Go, ARM, and Terraform.

Key use circumstances for this service

  • Conditionally ahead from on-premises with Azure ExpressRoute/VPN and resolve names hosted on Azure Personal DNS Zones by way of non-public IP deal with.
  • Seamlessly resolve Personal Endpoints that are registered in Azure Personal DNS Zones.
  • Configure default DNS servers and ahead all DNS queries to both a Protecting DNS service or different goal DNS servers with a wildcard rule.
  • Conditionally ahead to any reachable goal DNS server utilizing a easy rule.
  • Entry assets on-premises with Azure Bastion utilizing names hosted on DNS servers on-premises or Azure Personal DNS zones.

Absolutely managed

Constructed-in excessive availability, zone redundancy, and low latency title decision.

Reduces price

Cut back working prices and run at a fraction of the value of conventional IaaS options.

Personal entry to your Personal DNS Zones

Conditionally ahead out of your Digital Networks to any reachable DNS server and from on-premises to Azure Personal DNS Zones.


Excessive efficiency per endpoint.

Extremely accessible

Availability Zone conscious and resilient to failures inside a area. Service-legal settlement (SLA) of 99.99 p.c throughout common availability.


Construct your pipelines with Terraform, ARM, or Bicep.

Get began and share your suggestions

You may attempt Azure DNS Personal Resolver in the present day. For extra details about the capabilities accessible, please go to the Azure DNS Personal Resolver technical documentation webpage. Put up your concepts and solutions on the networking group web page.


Please enter your comment!
Please enter your name here