Search
- Filter results by:
- View attachments
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/nslookup_command_could_not_resolve_vserver_host_nameApplies to ONTAP 9 Name Services Issue nslookup command could not resolve the vserver host name
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/AutoSupport_delivery_fails_due_to_DNS_Couldn_t_resolve_host_in_ONTAP_9_and_earlierAutoSupport delivery fails due to DNS servers unable to resolve host in ONTAP 9 and earlier. This article covers some of the common causes and the solution to resolve these issues.
- https://kb.netapp.com/Cloud/Astra/Trident/Requesting_a_persistent_volume_in_Trident_returns_with_an_EOF_error/etc/resolv.conf in worker nodes have a "search domains" directive, that works as expected pods running on these worker nodes will inherit options and search domains from their host, and add a ndots:5.../etc/resolv.conf in worker nodes have a "search domains" directive, that works as expected pods running on these worker nodes will inherit options and search domains from their host, and add a ndots:5 directive pods only resolve FQDNs, but when removing "ndots:5" or search domains inside the pod, the pod is able to resolve any name an ONTAPI https request test to the SVM shows that it's responding normally to, for example a system-get-version API call (*)
- https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/Can_I_use_Anycast_DNS_on_Active_IQ_Unified_ManagerApplies to Active AIQUM Unified Manager (AIQUM) 9.x Yes, AnyCast can be used as long as the DNS resolves to the correct IP addresses. Configuring the AIQUM network settings in IPv6 is not supported. D...Applies to Active AIQUM Unified Manager (AIQUM) 9.x Yes, AnyCast can be used as long as the DNS resolves to the correct IP addresses. Configuring the AIQUM network settings in IPv6 is not supported. Doc: Active IQ Unified Manager does not work in a pure IPv6 environment When adding clusters to AIQUM you may use either IPv4 or IPv6 addresses. The hostname of the cluster has to be resolved to the IP of the cluster management LIF. Doc: Requirements for host connectivity
- https://kb.netapp.com/hybrid/StorageGRID/Object_Mgmt/StorageGRID_reports_502_proxy_error_the_StorageGRID_API_service_is_not_respondingApplies to NetApp StorageGRID Issue When trying to access the SANtricity System Manager from StorageGRID, it reports: 502 proxy error. The StorageGRID API service is not responding. Please try again l...Applies to NetApp StorageGRID Issue When trying to access the SANtricity System Manager from StorageGRID, it reports: 502 proxy error. The StorageGRID API service is not responding. Please try again later. If the problem persist, Contact Technical Support. Details: API Version: 3.3
- https://kb.netapp.com/data-mgmt/SnapCenter/SC_KBs/SnapCenter_does_not_allow_to_add_Domain_Controller_IP_for_untrusted_domain_from_GUIApplies to SnapCenter server 4.1 and later Issue When attempting to add an untrusted domain to SnapCenter, it is not possible to add the correct IP address to the domain controller. When Resolve is cl...Applies to SnapCenter server 4.1 and later Issue When attempting to add an untrusted domain to SnapCenter, it is not possible to add the correct IP address to the domain controller. When Resolve is clicked in the Add Domain, it resolves to an incorrect IP address, or you need to redirect the domain traffic from SnapCenter to a different domain controller.
- https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/Modifying_DNS_configuration_of_ONTAP_Deploy_instanceApplies to NetApp ONTAP Select Deploy Description ONTAP Select Deploy does not support a direct DNS configuration change. Below procedure is a workaround for changing ONTAP Select Deploy DNS configura...Applies to NetApp ONTAP Select Deploy Description ONTAP Select Deploy does not support a direct DNS configuration change. Below procedure is a workaround for changing ONTAP Select Deploy DNS configuration.
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/LIF_is_no_longer_listening_on_DNS_portONTAP maintains DNS load balance. The DNS Server notices the following error. LIF is no longer listening on the DNS port. And observe that the DNS queries received ICMP Port unreachable responses in t...ONTAP maintains DNS load balance. The DNS Server notices the following error. LIF is no longer listening on the DNS port. And observe that the DNS queries received ICMP Port unreachable responses in the packet trace. 1 2022-04-15 12:00:55.172117 0.000000 192.168.34.6 192.168.200.1 DNS 81 Standard query 0x0673 A domain.com 2 2022-04-15 12:00:55.172152 0.000035 192.168.200.1 192.168.34.6 ICMP 70 Destination unreachable (Port unreachable) DNS port is non-reachable.
- https://kb.netapp.com/Legacy/ONTAP/7Mode/AutoSupport_delivery_fails_due_to_DNS_Couldn_t_resolve_host_in_Data_ONTAP_7_modeData ONTAP 7-mode Nodes could not connect to the DNS servers and could not resolve any of the following host names. Run command Autosupport history show Data ONTAP 8 >autosupport history show >autosup...Data ONTAP 7-mode Nodes could not connect to the DNS servers and could not resolve any of the following host names. Run command Autosupport history show Data ONTAP 8 >autosupport history show >autosupport history show -fields seq-num,status,error,destination Last Error reported : Couldn't resolve host name. Attempting to deliver ASUP using PUT) 829:1528:deliver) (emittime: 2/27/2015 02:27:01) (message: Couldn't resolve host
- https://kb.netapp.com/data-mgmt/AIQUM/AIQUM_Kbs/The_OCIE_service_of_ActiveIQ_UM_fails_to_start_because_of_an_incorrect_DNS_entryApplies to ActiveIQ Unified Manager (UM) 9.7 Issue The UM ocie service fails to start There is no clear releated error in /var/log/ocie/server.log The deployment file /opt/netapp/essentials/jboss/stan...Applies to ActiveIQ Unified Manager (UM) 9.7 Issue The UM ocie service fails to start There is no clear releated error in /var/log/ocie/server.log The deployment file /opt/netapp/essentials/jboss/standalone/deployments/dfm-app.war fails to deploy
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/DNS_timeouts_cause_secd_ldap_noServers_messages_every_4_hoursSun May 15 12:29:54 HKT [nodeA: secd: secd.ldap.noServers:EMERGENCY]: None of the LDAP servers configured for Vserver (NAS11) are currently accessible via the network for LDAP service type (Service: L...Sun May 15 12:29:54 HKT [nodeA: secd: secd.ldap.noServers:EMERGENCY]: None of the LDAP servers configured for Vserver (NAS11) are currently accessible via the network for LDAP service type (Service: LDAP (Active Directory), Operation: SiteDiscovery). Sun May 15 20:15:48 HKT [nodeA2: secd: secd.dns.srv.lookup.failed:error]: DNS server failed to look up service (_ldap._tcp.dc._msdcs.local.domain.net) for vserver (NAS11) with error (Operation timed out).