Azure Private DNS Zone resolution from OnPremise
Make it possible to enable the Name Resolution from onpremise if i have an azure private dns Zone.
It should be possible to make an Forward from onpremise dns to an azure private dns Zone.
+3 from me. Seems really dumb to run a VM just to handle DNS forwarding for one thing that should be integrated...
Is there any update on an ETA for this or any newer ways to address both on-prem to Azure and Azure to on-prem internal zones without custom IaaS DNS servers? It’s a bit crazy to need IaaS purely for DNS resolution when we are trying to keep Azure PaaS and SaaS. Conditional or Authoritative DNS is absolutely needed in Azure DNS or at least in Azure Firewall.
Any updates from Microsoft there?
Erik van Ast commented
This would be really useful....
Shmatenkov, Nikolai commented
+1 Almost 2 years in the planned state. Microsoft Azure Team, can you provide any ETA about that?
Leonardo Santos commented
+1 This would be extremely useful for when connecting to Azure over P2S VPN Connections. Having intermediary VM's with the sole purpose of being a DNS Forwarder is very, very far from ideal. Shame it is not in place yet after being in the 'Planned' status for so long.
Any update/private preview we can onboard too, currently having to manage our own DNS (owned by separate team to CloudOps) makes following the new ESLZ decentralised model difficult as it requires separate tickets for new child domains as business units onboard to Azure and then providing additional tools to manage it.
+1 from another organisation surprise that the Azure VPN doesn't forward DNS from the VNet.
Please solve this ASAP.
we are connecting to azure over P2S VPN Connections. I can't understand, why "privatelink.database.windows.net" is not resolved correctly....
And after closing down SQL Servers to only use private links to communicate, this missing DNS forwarding to Azure DNS servers is extremely annoying.
How should the Devs. connect to the DB ?
Does Microsoft have any updates on this "planned" feature? Is it planned for this decade?
Kozak, Daniel commented
Definitely need this functionality. Especially with the trend towards PaaS/Serverless environments, I would really prefer not to have to create a VM just to forward the DNS back to Azure DNS server for my point to site VPN.
Marcus Brito commented
We wating for it... Please MS, deliver it to us.
Fausto Sakamoto commented
It would be great to eliminate the intermediary VMs for DNS query forwarding. Less points of failure, more scalability and reliability. Please MS, deliver it to us.
Linu Raj commented
We are also looking for a scalable and reliable solution for this. Would you be able to help us?
It would be great to resolve private endpoints FQDNs without using an extra VM as a DNS Forwarder.
Vincent Smit commented
Is this already working with Azure S2P VPN Connections? We've tested it today and it seems some workstations/laptops resolve our SQL servers using the private endpoint while others resolve towards the external IPs..
Boudewijn Plomp commented
There is a kind of intermediate solution; configure the the Azure Firewall as DNS Forwarder/Proxy. This work, but is missing a features like 'DNS Conditional Forwarding'.
Often you need a central DNS Server (IaaS) on Azure. Not only to provide name-resolution within a Hub-
Spoke Model and able to resolved Private DNS Zones. But also to provide name resolution from- and to on-premise DNS Server.
Andre Reis commented
I Tested today and Worked, using Vpn p2s :) But i didnt find any documentation that says its implemented
Matt Syracuse commented
If the direction is to use Private Link and Private Endpoints - DNS is the key element to make this work from on-premise. This needs to be easier and not a barrier.
can we get an update on this please Azure team?
shame on you Azure