Does not see that the server role failed over to a another node

Homestart Finance ExternaltestAccount 1 Reputation point
2022-01-26T23:38:42.51+00:00

Hi, Everyone.

Please help me with an issue we are encountering. Currently we have Windows Failover Cluster with SQL. If we ping the name of the role it is replying but once we fail over the cluster role to another node, the ping was not able to recover. It still says timeout. The only way to make this work again is by doing "ipconfig /flushdns" I have configured the TTL of the cluster role name to 20 seconds but still is the same problem. Any suggestion on how to address this?

I have tested this in multiple machine and it is the same problem

Windows DHCP
Windows DHCP
Windows: A family of Microsoft operating systems that run across personal computers, tablets, laptops, phones, internet of things devices, self-contained mixed reality headsets, large collaboration screens, and other devices.DHCP: Dynamic Host Configuration Protocol (DHCP). A communications protocol that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
942 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
762 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Homestart Finance ExternaltestAccount 1 Reputation point
    2022-01-27T02:33:43.087+00:00

    I have found out that the TTL has changed back to 20 minutes. I have change it again all AD in our domain but still it went back to 20 minutes. Any information why this is happening?