Skip to main content
NetApp Knowledge Base

What should be considered when replacing a CIFS shared storage system that has DNS CNAME records and SPNs registered

Views:
32
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
NAS
Last Updated:

Applies to

ONTAP 9

Answer

  • To replace the current CIFS shared storage without changing the access method, which uses legacy hostnames. 
  • Need to ensure proper DNS and SPN configurations to maintain seamless access.
  1. DNS Configuration:
  • Retain the record for the current host name.
  • Remove the CNAME record pointing from the previous host name to the current host name.
  • Add a new record for the previous host name pointing to the new host's IP address.
  • Example:
    • Current Host Name A Record: Keep as is.
    • Previous Host Name to Current Host Name CNAME Record: Remove.
    • Previous Host Name A Record: Add pointing to New Host IP.
  1. SPN Configuration:
  • Retain the SPN entries for the current host name.
  • Remove the SPN entries for the previous host name.
  • Add new SPN entries for the previous host name pointing to the new host.
  • Example:
    • Current Host Name: Keep as is.
    • Previous Host Name: Remove.
    • New Host Name: Add SPN entries.

Additional Information

  • Ensure that the DNS and SPN changes are properly propagated and verified before decommissioning the old storage.
  • It is recommended to perform these changes during a maintenance window to minimize impact on users.
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.