topic Re: Azure Databricks unable to connect to private DNS KeyVault in createScope, showing "DNS invalid" in Data Engineering

Azure Databricks unable to connect to private DNS KeyVault in createScope, showing "DNS invalid"

Nilave — Sun, 08 May 2022 10:38:54 GMT

I have an Azure KeyVault with private endpoint created in the same Vnet as Azure Databricks. While trying to add it as a scope using the private DNS Zone ie <KVname>.privatelink.vaultcore.azure.net

getting error "DNS is invalid and cannot be reached."

If I try to ping it from Azure Databricks using as below

%sh ping <KVName>.privatelink.vaultcore.azure.net , it does resolves to its private IP address.

What could be the issue

Re: Azure Databricks unable to connect to private DNS KeyVault in createScope, showing "DNS invalid"

Soma — Fri, 07 Oct 2022 05:28:51 GMT

hi @Kaniz Fatma @Nilave Chakraborty still facing the same issue.

The solution you have provided is not working and in this case the key vault dns itself not getting resolved.

Can you please let me know how this got resolved

Re: Azure Databricks unable to connect to private DNS KeyVault in createScope, showing "DNS invalid"

mark_362882 — Tue, 10 Jan 2023 10:08:13 GMT

This is not the answer.

I have the same question.

How can I connect an Azure Key Vault with private endpoint to the databricks vnet?

Re: Azure Databricks unable to connect to private DNS KeyVault in createScope, showing "DNS invalid"

mark_362882 — Tue, 10 Jan 2023 10:40:59 GMT

I got it working by creating the KV backed scope via UI. I used the the dns without the private part: <KVName>.vault.azure.net

The private dns will resolve it to the right IP.

You do have to check the "Allow trusted Microsoft services to bypass this firewall" in the Firewalls and virtual tab if you have set Allow access from to disable public access or Allow public access from specific virtual networks and IP addresses.