Skip to content

Commit efc596f

Browse files
authored
Update sql-ag-use-dnn-listener.md
1 parent b55201e commit efc596f

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

azure-sql/includes/sql-ag-use-dnn-listener.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,4 +7,4 @@ ms.topic: include
77
---
88

99
> [!NOTE]
10-
> Availability group deployments to [multiple subnets](../virtual-machines/windows/availability-group-manually-configure-prerequisites-tutorial-multi-subnet) don't require a load balancer. In a single-subnet environment, customers who use SQL Server 2019 CU8 and later on Windows 2016 and later can replace the traditional virtual network name (VNN) listener and Azure Load Balancer with a [distributed network name (DNN) listener](../virtual-machines/windows/availability-group-distributed-network-name-dnn-listener-configure.md). If you want to use a DNN, skip any tutorial steps that configure Azure Load Balancer for your availability group.
10+
> Availability group deployments to [multiple subnets](../virtual-machines/windows/availability-group-manually-configure-prerequisites-tutorial-multi-subnet.md) don't require a load balancer. In a single-subnet environment, customers who use SQL Server 2019 CU8 and later on Windows 2016 and later can replace the traditional virtual network name (VNN) listener and Azure Load Balancer with a [distributed network name (DNN) listener](../virtual-machines/windows/availability-group-distributed-network-name-dnn-listener-configure.md). If you want to use a DNN, skip any tutorial steps that configure Azure Load Balancer for your availability group.

0 commit comments

Comments
 (0)