Skip to main content
NetApp Knowledge Base

Hostname does not resolve in Azure CVO

Views:
325
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
microsoft_azure
Last Updated:

Applies to

  • Cloud Volumes ONTAP
  • BlueXP
  • Azure
  • Page blobs

Issue

  • Raid status of a data aggregate shows tier_unavailable.
  • After setting up private endpoints to storage accounts, DNS and objstore.host.unresolvable errors began to spam frequently.
[?]  Tue Jan 07 14:20:11 +0000 [node-01: OscHighPriThreadPool: objstore.host.unresolvable:error]: Object-store server host name "storageaccountname.blob.core.windows.net" cannot be resolved to an IP address on node xxxxxx.
 
[?]  Tue Jan 07 00:42:25 +0000 [node-01: secd: secd.unexpectedFailure:error]: Unexpected SecD failure in Vserver "admin". Details: Error: DNS forward lookup procedure failed   [ 39 ms] Entry for host-name: storageaccountname.blob.core.windows.net not found in any of the available sources **[    49] FAILURE: Hostname lookup failed with error: Name does not resolve

Cause

  • When aggregate was created in BlueXP, BlueXP created it's own Private DNS zone in Azure different from what was primarily used.
  • The storage account DNS was not listed in Recordsets for the proper Private DNS zone.

Solution

 Add missing Recordsets for affected storage accounts to proper Private DNS zone.

Note: DNS Recordset may need to be added to Local DNS Server in DNS Manager.

Partner Notes

partnerNotes_text
 

Additional Information

additionalInformation_text

Internal Notes

 
Resolution for case 2010284751 was to add missing Recordsets for affected storage accounts to proper Private DNS zone.

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.