Unable To Resolve Azure Private DNS Zone with Linked Virtual Network

devopsfj 46 Reputation points

I am having an issue, which may be by design, however I need confirmation.

I have a Virtual Network which is linked to a Private DNS Zone, name resolution worked fine, since then, I have changed the DNS Servers for the Virtual Network from Azure Provided to our custom DNS Servers, since this change, I can no longer resolve the Private DNS Zone's even though they are still linked, is this expected behaviour?

Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
443 questions
Azure Virtual Network
Azure Virtual Network
An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
1,394 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sruthi Saranya Karthikeyan 231 Reputation points Microsoft Employee

    Hi @devopsfj ,

    This is expected behaviour as the Private DNS Zone records can be accessed and resolved by Azure DNS only. The workaround for this particular situation can be to setup a DNS forwarder VM on the virtual network and setup conditional forwarding on your custom DNS servers to forward the requests for the private domain to the forwarder VM on the Azure Vnet.

    Hope this helps.


1 additional answer

Sort by: Most helpful
  1. Gregory Grskovich 1 Reputation point

    Why do you need a separate VM as a forwarder? Why does this not work with the conditional forwarder sending directly to the Azure DNS IP or alternatively having the Azure IP set as your forwarder on your custom DNS servers. I've tried both and neither works.