![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 25%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERV%3C/text%3E%3C/svg%3E)
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
675 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 11%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJZ%3C/text%3E%3C/svg%3E)
Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
If you were to update the DNS Server of the Azure VNET to a custom DNS Server residing at OnPrem,
- All the DNS Queries would go to the OnPremises DNS Server only
- Even the DNS queries of PaaS Services will be forwarded to the OnPrem DNS Server.
- It does not make sense to have the Private DNS Zone linked to a VNET which uses a custom DNS Server.
In such scenarios,
- It is recommended to use the Azure Private DNS Resolver.
- You should use Azure Private Resolver directly for VMs located in Azure
- And use Azure DNS forwarding ruleset to forward queries to OnPrem that are not covered by Azure Private DNS Zones
- And for OnPrem servers, you should forward the DNS requests from the OnPrem DNS Server to the Azure Private Resolver using a conditional forwarder.
You can create such a hybrid DNS architecture as defined in Resolve Azure and on-premises domains
Thanks,
Kapil
Please Accept an answer if correct.
Original posters help the community find answers faster by identifying the correct answer.