Skip to main content
NetApp Knowledge Base

ONTAP persistently discovers DC server list from old AD site after modifying default AD site to new one

Views:
573
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • Active Directory (AD) Site
  • Domain Controller (DC)

Issue

ONTAP persistently discovers the DC server list from old AD site after modifying default AD site to new one.

  • Modify the CIFS server configuration, change the default site to "TK".
  • Packet trace shows the ONTAP is still querying the DC server from the old site of "DL"

2021-05-18 15:54:29 10.xx.xx.xx 10.xx.xx.xx DNS Standard query 0x7bec SRV _ldap._tcp.DL._sites.dc._msdcs.tse.com
2021-05-18 15:54:29 10.xx.xx.xx 10.xx.xx.xx DNS Standard query response 0x7bec SRV _ldap._tcp.DL._sites.dc._msdcs.TSE.com SRV 0 100 389 win2016-dc1.tse.com SRV 0 100 389 win2016-dc2.tse.com SRV ......

  • The AD site information shows differences between client site and server site. 

::*> secd authentication get-dc-info -node ontap96-02 -vserver svm1_ontap96

   DC Information:
   ---------------
           Forest: tse.com
           Domain: tse.com
     NetBIOS Name: TSE
 NetBIOS Hostname: WIN2016-DC1
      Server Site: TK
      Client Site: DL

        

 

 

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.