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.
Jack Chen commented
hit this issue as well. One issue I see is Azure DNS doesn't answer query with "Don't query recursively" option.
Nivas Y commented
+1 we need this for integrations with our onPrem infra as as well as those of our customers.
Bill Stoddart commented
Our use case i think is a bit unique as we are 100% hosted in the cloud (Azure). We just have enough gear in the office to connect us to the internet. Our folks all connect to the network resources using P2S VPN client. Being able to use an FQDN to access private Azure resources would be awesome!
Ryan Adler commented
This is key for us to be able to properly restrict access to resources!
Nathan Becker commented
We're also experiencing some pain with this. We're using Private Link to restrict access to our on-prem network, but since we can't forward on-prem queries directly to Azure DNS, we have to set up and maintain a VM, which is a headache.
On-prem systems not being able to forward the queries to Private DNS forces to maintain some of the records [that need a resolution from on-prem] on Public DNS zones. This is super inefficient and in a way solves half of the problem only.
Phillip Hamlyn commented
Attempting to use Private Link to SQL Azure, but cannot connect to the SQL via P2S VPN because name resolves to public IP address.
Daniel Griggs commented
Please don't just make it a resolver, being authoritative for the zone it's serving is a must.
Also hitting this wall, p2s VPN, unable to resolve custom private domains, very frustrating
AWS has provided a service of name resolution between Amazon Route 53 Private hosted Zone and On-Premise using Route 53 Resolver, so it would be great if a similar feature is released in Azure.
would significantly help to stream line our deployment code and touch points.