There is a known issue with targeting
net5.0 on Azure App Service and trying to connect to Elasticsearch on a virtual machine connected to via an Azure VNet. The main ticket is here:
The issue is essentially that .NET 5.0's
HttpClient is trying to use IPv6 wherever it's supported. The .NET runtime's team has a suggested workaround where you force
HttpClient to use IPv4:
Question: is it possible to customize
NEST's creation of
HttpClient instances to force it to use IPv4 sockets as described in the workaround above?