%3CLINGO-SUB%20id%3D%22lingo-sub-1796546%22%20slang%3D%22en-US%22%3EReleased%3A%20Support%20for%20Dynamic%20Network%20Names%20(DNN)%20Listeners%20for%20Always%20On%20Availability%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1796546%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%20size%3D%225%22%3EAs%20of%20SQL%20Server%202019%20CU8%2C%20we%20now%20support%20the%20use%20of%20Availability%20Group%20Listeners%20based%20on%20Dynamic%20Network%20Names%20(DNN%20Listeners).%3C%2FFONT%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDNN%20listeners%20are%20especially%20useful%20in%20Azure%20VM%20environments%2C%20as%20they%20eliminate%20the%20need%20to%20configure%20Azure%20Load%20Balancers%2C%20thus%20simplifying%20the%20configuration%20and%20setup.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDNN%20resources%20were%20introduced%20to%20Windows%20Failover%20Clusters%20in%20Windows%20Server%202016%2C%20and%20have%20been%20available%20for%20use%20with%20SQL%20FCIs%20previously.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EDynamic%20Network%20Names%20are%20a%20feature%20which%20has%20been%20supported%20in%20Windows%20Failover%20Clusters%3C%2FP%3E%0A%3CP%3ETo%20learn%20more%2C%20start%20with%20the%20Availability%20Group%20overview%20topic%20in%20the%20documentation%2C%20in%20a%20new%20section%20about%20DNN%20listeners%3A%26nbsp%3B%3CA%20title%3D%22Availability%20Group%20Overview%20-%20DNN%20Listener%22%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fazure-sql%2Fvirtual-machines%2Fwindows%2Favailability-group-overview%23dnn-listener%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EAvailability%20Group%20Overview%20-%20DNN%20Listener%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1796546%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20are%20peased%20to%20announce%20support%20for%20Dynamic%20Network%20Name%20based%20listeners%20in%20Availability%20Groups.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20of%20SQL%20Server%202019%2C%20CU8%2C%20we%20now%20support%20the%20use%20of%20Availability%20Group%20Listeners%20based%20on%20Dynamic%20Network%20Names%20(DNN%20Listeners).%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1796546%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESQLServerAlwaysOn%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESQLServerAzureVM%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1802858%22%20slang%3D%22en-US%22%3ERe%3A%20Released%3A%20Support%20for%20Dynamic%20Network%20Names%20(DNN)%20Listeners%20for%20Always%20On%20Availability%20Groups%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1802858%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%20what's%20the%20GA%20date%20for%20DNN%20%3F%3C%2FP%3E%0A%3CP%3EAny%20performance%20comparison%20between%20DNN%20vs%20using%20Load%20balancer%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

As of SQL Server 2019 CU8, we now support the use of Availability Group Listeners based on Dynamic Network Names (DNN Listeners).

 

DNN listeners are especially useful in Azure VM environments, as they eliminate the need to configure Azure Load Balancers, thus simplifying the configuration and setup.  

 

DNN resources were introduced to Windows Failover Clusters in Windows Server 2016, and have been available for use with SQL FCIs previously.

 

Dynamic Network Names are a feature which has been supported in Windows Failover Clusters

To learn more, start with the Availability Group overview topic in the documentation, in a new section about DNN listeners: Availability Group Overview - DNN Listener  

2 Comments
Microsoft

Hi. what's the GA date for DNN ?

Any performance comparison between DNN vs using Load balancer ?

Microsoft

The feature is GA now. (as of SQL2019 CU8 for availability Groups, CU2 for Failover Cluster Instances).

DNN is only involved in establishing the connection, so there is no difference at all once the connection is established.

My understanding is that failover times will be slightly better, and there should be a very small delta in connection times, mostly due to less network hops through the Load Balancer.