DNN Listener resolving to a secondary server in WSFC & AO AG
-1
votes
4
answers
2994
views
I have an Azure AO AG which consists of three servers (all WS-2019 & SQL-2019 CU8):
- A - Subnet 1 - Principal Server (Sync)
- B - Subnet 1 - Secondary Server (Sync)
- C - Subnet 2 - Secondary Server (Async)
I have created a DNN Listener on the resource which looks to be up an running but when I connect to the Listener it resolves to server C. I have confirmed that in the cluster and AG, server A is the principal. I have tried failing over to server B which seems to work fine but the listener still only resolves to Server C.
I pulled out the Cluster Logs and I have a warning that jumped out to me that does not seem to appear on google:
2020/11/12-15:27:48.720 WARN [RES] Distributed Network Name : Configuration: Obtaining exclude networks failed with error 2.
Asked by Lickrob
(84 rep)
Nov 13, 2020, 09:57 AM
Last activity: Nov 1, 2021, 06:29 AM
Last activity: Nov 1, 2021, 06:29 AM