SQL Server Standard Basic Availability Group - only 10 Listeners limit? Is there a limit to the number of listeners that can be created using SQL Server Standard?

I'm working with a DBA who has set up a 2017 Standard server, with CU3. We have 12 databases, and he was able to set up 12 basic availability groups. He was able to set up 10 listeners, but on the 11th, is getting the error below:


  Create failed for Availability Group Listener 'test12300'.  (Microsoft.SqlServer.Smo)
  
  For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&amp;ProdVer=14.0.17213.0+((SSMS_Rel).171128-2020)&amp;EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&amp;EvtID=Create+AvailabilityGroupListener&amp;LinkId=20476
  
  
  
  ADDITIONAL INFORMATION:
  
  An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
  
  
  
  The WSFC cluster could not bring the Network Name resource with DNS name 'test12300' online. The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information.
  The attempt to create the network name and IP address for the listener failed. If this is a WSFC availability group, the WSFC service may not be running or may be inaccessible in its current state, or the values provided for the network name and IP address may be incorrect. Check the state of the WSFC cluster and validate the network name and IP address with the network administrator. Otherwise, contact your primary support provider. (Microsoft SQL Server, Error: 19471)
  
  For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&amp;ProdVer=14.00.3015&amp;EvtSrc=MSSQLServer&amp;EvtID=19471&amp;LinkId=20476


We created 11 empty databases, backed up each, and then through the AG Wizard created an AG and a Listener using DHCP. It worked 10 times, but on the 11th it failed. For the 11th listener, we chose name BAG_L11, there is nothing else that uses that DNS name.
The limitation is only number of replicas.

Limit of two replicas (primary and secondary).
he was able to set up 12 basic availability groups. He was able to set up 10 listeners

You can create many AGs and listeners. The error you are getting is self explanatory

The DNS name may have been taken or have a conflict with existing name services, or the WSFC cluster service may not be running or may be inaccessible. Use a different DNS name to resolve name conflicts, or check the WSFC cluster log for more information.

Also refer to Top 7 Questions about Basic Availability Groups and Troubleshooting AlwaysOn availability group listener creation in SQL Server 2012.