Deployment of two private endpoint, for same KeyVault is overwriting 'A' record in the private DNS zone

[sujitks]

key-vault-private-endpoint

Issue Details

Deployment of two private endpoint, for same KeyVault is overwriting 'A' record in the private DNS zone

Repro steps (if necessary, delete otherwise)

Private DNS is a global resource, this means we can use same instance to link with two separate isolated network from two separate region.

For example, we have a KeyVault (uksouthsample.vault.azure.net) in UK South region, we have a private endpoint deployed to access Key Vault in UK south. This will create an 'A' record in the privatelink.vaultcore.azure.net DNS Zone.

If we create another network in UK West, link that network with the same private DNS zone resource and try to deploy a private endpoint in UK West for the same Key Vault in UK South (uksouthsample.vault.azure.net), it overwrites the 'A' record uksouthsample in the privatelink.vaultcore.azure.net.

Is there any way to address this? Or we must create a separate private DNS zone resource to use with vNet in UK West?