A virtual network cannot be linked to multiple zones with overlapping namespaces.

Question

A virtual network cannot be linked to multiple zones with overlapping namespaces.

Nico Albarracin 0

I'm trying to create a Virtual Network Link to the private DNS zone privatelink.azurewebsites.net, but I consistently receive the following error:

"A virtual network cannot be linked to multiple zones with overlapping namespaces. You tried to link virtual network with 'privatelink.azurewebsites.net' and 'privatelink.azurewebsites.net' zones."

Context:

At one point, we accidentally had two private DNS zones named privatelink.azurewebsites.net in our environment.

We attempted to create a VNet link to one of them, but it failed.

We then deleted the duplicate DNS zone, expecting the issue to be resolved.

However, now whenever we try to create a new VNet link to the remaining privatelink.azurewebsites.net zone, we still get the same error, even though only one zone with that name exists, and no links show up in the portal or via CLI.

Steps Already Taken:

Confirmed via az network private-dns link vnet list that there are no active VNet links

Verified that only one privatelink.azurewebsites.net zone exists in the subscription

Checked for resource locks or leftover private endpoint bindings

Attempted deletion and recreation of the DNS zone (still blocked)I'm trying to create a Virtual Network Link to the private DNS zone privatelink.azurewebsites.net, but I consistently receive the following error:

"A virtual network cannot be linked to multiple zones with overlapping namespaces. You tried to link virtual network with 'privatelink.azurewebsites.net' and 'privatelink.azurewebsites.net' zones."

G Sree Vidya 4,080 Reputation points Microsoft External Staff Moderator

2025-06-13T05:10:57.49+00:00

Hello @Nico Albarracin

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
G Sree Vidya 4,080 Reputation points Microsoft External Staff Moderator

2025-06-16T07:36:16.1233333+00:00

Hi @Nico Albarracin

Following up to see if the below information was helpful. And, if you have any further query do let us know.

Please don’t forget to close the thread by clicking "Accept the answer" and "Yes" wherever the information provided helps you, as this can be beneficial to other community members.

1 answer

Your answer

G Sree Vidya 4,080 Reputation points Microsoft External Staff Moderator

2025-06-13T05:10:57.49+00:00

Hello @Nico Albarracin

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
G Sree Vidya 4,080 Reputation points Microsoft External Staff Moderator

2025-06-16T07:36:16.1233333+00:00

Hi @Nico Albarracin

Following up to see if the below information was helpful. And, if you have any further query do let us know.

Please don’t forget to close the thread by clicking "Accept the answer" and "Yes" wherever the information provided helps you, as this can be beneficial to other community members.

Answer 1

Hello @Nico Albarracin

I understand that you are facing issue with the Virtual Network Link.

"A virtual network cannot be linked to multiple zones with overlapping namespaces..."

This caused by Azure's restriction that a single virtual network (VNet) cannot be linked to more than one Private DNS Zone with the same namespace, even if the zones were previously deleted or appear to be gone.

Even though you've deleted the duplicate privatelink.azurewebsites.net zone, Azure may still have residual metadata or stale link references associated with the VNet. These can persist in the background and block new links from being created.

1.Use one privatelink.azurewebsites.net zone across all subscriptions and link it to all relevant VNETs. Avoid creating multiple zones with the same name as per the Microsoft document:

Refer: https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-dns-integration

Sharing you the similar thread for your reference: https://learn.microsoft.com/en-us/answers/questions/861192/deployment-failed-a-virtual-network-cannot-be-link

Here how you can fix using below steps:

Even if you see only one privatelink.azurewebsites.net zone in your current subscription, there might be:

A duplicate zone in another subscription or resource group
A zombie link that was not properly deleted

Use this command to list all private DNS zones across subscriptions (if you have access):

az`` network private-dns zone list --query "[?name=='privatelink.azurewebsites.net']"
Use Azure CLI to forcefully delete any ghost links: If you find any links, delete them using:

az`` network private-dns link vnet delete \
  ``--resource-group <resource-group-name> \
  ``--zone-name privatelink.azurewebsites.net \
  ``--name <link-name>

Check for links in other subscriptions or regions: Sometimes the conflict comes from a zone or link in a different subscription or resource group that’s still active.

Wait for propagation: After deleting a DNS zone or link, it can take a few minutes to fully propagate. Wait 10–15 minutes before retrying the link creation.

If all else fails:

Try creating a new VNet and linking it to the DNS zone to confirm the issue is with the original VNet.
Or open a Microsoft support ticket to clear any hidden metadata.

I hope this information is helpful! If my answer helped you resolve your issue, please consider marking it as the correct answer or Upvote. This helps others in the community find solutions more easily. Thanks!

Share via

A virtual network cannot be linked to multiple zones with overlapping namespaces.

1 answer

Your answer