I am working on creating an AG on SQL Server 2017 Standard and Windows Server 2016. I have created the failover cluster using a file share witness and everything checks out OK with the cluster. The only issue or warnings I get are related to only using 1 NIC for each server (These are VM's with multiple NIC's). I can connect to the SQL instance using the windows failover cluster DNS entry. When I down one server or manually fail over the cluster, the cluster DNS entry does not update to point to the new "failed over IP" These 2 different IP's are on 2 separate subnets. After some time (20 minutes) the DNS entry will update to the new (failed over) IP. I have tried to adjust the TTL setting in the cluster name DNS entry however, it changes itself back to 20 minutes. What am I missing here?
Sql-server – SQL 2017 Standard Availability Group
sql-server-2017windows-server
Related Question
- Windows – Cluster network name resource ‘Cluster Name’ failed registration
- SQL Server 2017 CU3 – Adding Read-Scale Replica Issue
- SQL Server 2014 Standard FCI – Troubleshooting Failover Issues
- Sql-server – Is it safe to run a Windows Failover Cluster Public and Heartbeat on a Single NIC
- SQL 2017 on Windows Server 2019 – Fix Availability Group Listener IP Issue
- SQL Server 2017 – Always On High Availability Groups Multi Subnet
- Sql-server – SQL Server 2017 Availability Group Deployment – Some availability replicas are not synchronizing data
Best Answer
As you don't mention it, I suspect your application is not connecting with
SqlClient Support for High Availability, Disaster Recovery