DNS not responding cause secd.ldap.noServers messages
Applies to
- ONTAP 9
- Domain Name Service (DNS)
Issue
- Received a warning message：
XXX emergency secd secd.ldap.noServers:
None of the LDAP servers configured for Vserver (XXX) are currently
accessible via the network for LDAP service type (Service: LDAP (Active Directory), Operation: SiteDiscovery)- The following errors are logged in EMS:
59: [?] Tue Jul 15 08:39:21 +0900 [XXX: secd: secd.dns.server.timed.out:error]: DNS server XXX did not respond to vserver = XXX within timeout interval.
60: [?] Tue Jul 15 08:39:24 +0900 [XXX: secd: secd.conn.auth.failure:notice]: Vserver (XXX) could not make a connection over the network to server (ip XXX, port 389). Error: Operation timed out (Service: LDAP (Active Directory), Operation: SiteDiscovery).
61: [?] Tue Jul 15 08:39:24 +0900 [XXX: secd: secd.conn.auth.failure:notice]: Vserver (XXX) could not authenticate over the network to server (XXX). Error: Can't contact LDAP server (Service: LDAP (Active Directory), Operation: SiteDiscovery).
62: [?] Tue Jul 15 08:39:26 +0900 [XXX: secd: secd.conn.auth.failure:notice]: Vserver (XXX) could not make a connection over the network to server (ip XXX, port 389). Error: Operation timed out (Service: LDAP (Active Directory), Operation: SiteDiscovery).
63: [?] Tue Jul 15 08:39:26 +0900 [XXX: secd: secd.conn.auth.failure:notice]: Vserver (XXX) could not authenticate over the network to server (XXX). Error: Can't contact LDAP server (Service: LDAP (Active Directory), Operation: SiteDiscovery).
64: [?] Tue Jul 15 08:39:26 +0900 [XXX: secd: secd.ldap.noServers:EMERGENCY]: None of the LDAP servers configured for Vserver (XXX) are currently accessible via the network for LDAP service type (Service: LDAP (Active Directory), Operation: SiteDiscovery).
69: [?] Tue Jul 15 09:28:11 +0900 [XXX: secd: secd.conn.auth.failure:notice]: Vserver (XXX) could not make a connection over the network to server (ip XXX, port 88). Error: Operation timed out ().
97: [?] Tue Jul 15 17:26:11 +0900 [XXX: secd: secd.dns.server.timed.out:error]: DNS server XXX did not respond to vserver = XXX within timeout interval.- Errors might be seen in SECD:
00000024.001485c4 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] Failure Summary:
00000024.001485c5 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] Error: User authentication procedure failed
00000024.001485c6 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] CIFS SMB2 Share mapping - Client Ip = XXX
00000024.001485c7 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] [ 0 ms] Login attempt by domain user 'XXX\XXX' using NTLMv2 style security
00000024.001485c8 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] [ 0] No servers available for MS_NETLOGON, vserver: 3, domain: XXX.
00000024.001485c9 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] [ 5006] Failed to connect to XXX for DNS via Source Address XXX: Operation timed out
00000024.001485ca 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] [ 7008] Failed to connect to XXX for DNS via Source Address XXX: Operation timed out
00000024.001485cb 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] **[ 7010] FAILURE: Unable to contact DNS to discover domain controllers.
00000024.001485cc 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] [ 7010] Unable to make a connection (NetLogon:XXX), Result: RESULT_ERROR_DNS_CANT_REACH_SERVER
00000024.001485cd 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] [ 7010] CIFS authentication failed
00000024.001485ce 031eaced Tue Jul 15 2025 08:45:50 +09:00 [kern_secd:info:12920] [ 7010] Retry requested, but the retry window (7000 ms) has expired; giving up.- The following warning messages may also continue to be received.
XXX emergency secd secd.netlogon.noServers:
None of the Netlogon servers configured for Vserver (XXX) are currently accessible via the network.