How come Azure KeyVault Private DNS works differently to Azure SQL Servers?

Question

I have recently started Private Endpointing all of our infrastructure. As we are in Hub to Spoke environment we are using one Private DNS for each resource type which is then linked to the spokes and Hubs. We then create private endpoints for each resource which are associated with this Private DNS Zone.

We have finished the work for SQL Servers and noticed that we can access the Servers through the Private Endpoint and then when I do the following we get the correct response:

`nslookup mydatabase.database.windows.net

Answer 1

Hi @Liam Newton

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue: How come Azure Key Vault Private DNS works differently to Azure SQL Servers?

Solution: The problem appears to be caused by the firewall settings.

---

If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.