Skip to main content
NetApp Stage KB

Deploying a CVO and Azure Private DNS Zone in Different Regions

Views:
Visibility:
Public
Votes:
0
Category:
cloud-manager
Specialty:
CLOUD
Last Updated:

Applies to

  • Cloud Manager

  • Cloud Volumes ONTAP (CVO)

  • Azure Private Links

  • Azure Private DNS Zones

Issue

  • When deploying Cloud Volumes ONTAP and an Azure Private DNS Zone in different regions, Cloud Manager configures the VNET link from the private DNS zone to the region the CVO is being deployed in.

  • Cloud Manager tries to create a private DNS link (not storage account link but at VNET layer) but fails.

  • Cloud manager should not try to link the VNET to the private DNS zone because that is already configured.

  • Once that fails, Cloud Manager doesn't create private storage endpoints or updates the DNS zone records.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
df45308a-fc9e-46f4-8f5c-d83c851f3ef5