We have just updated the MySQL ASO.NET Connector on our Windows Servers to 8.2.0 to match the MySQL servers which have been upgraded to MySQL8. We are using the connector from within Microsoft SSIS jobs and found that it tried to access the MySQL database over IPv4 even though the both the Windows server and the server running the MySQL database had IPv6 IP addresses. Doing a simple ping to the same URL showed the IPv6 IP address. The ODBC connections to the same MySQL server worked flawlessly.
The workaround we figured out was to force the IPv6 IP address on the server by placing the URL and IPv6 IP address in the local machine's Hosts file.
Is there a known issue with the ADO.NET connector wanting to use IPv4 instead of IPv6? Are there any parameters which we can use to force IPv6 to be used each time. We currently have static DNS entries pointing to IPv6 IP addresses and if the admins ever changed the IP address of the MySQL database this would stop working until we matched this in the Hosts file.
The workaround we figured out was to force the IPv6 IP address on the server by placing the URL and IPv6 IP address in the local machine's Hosts file.
Is there a known issue with the ADO.NET connector wanting to use IPv4 instead of IPv6? Are there any parameters which we can use to force IPv6 to be used each time. We currently have static DNS entries pointing to IPv6 IP addresses and if the admins ever changed the IP address of the MySQL database this would stop working until we matched this in the Hosts file.