Using two certificates with SNI and IP as common name
I have a VS which client access using both FQDN and IP and I need it to be HTTPS.
I have a legitimate cert for the FQDN (wildcard) and I've created a certificate for the IP address using a CA we have inhouse.
I've also included SAN values for DNS and IP in this cert.
When I attach each certificate individualy to the VS and try to access it accordingly, everything works fine, so I know the certs are legit.
When I put both certs in the VS and configure their SSL profile with Default SNI and ServerName, it also selects the FQDN cert, even if the client access using IP address.
Any suggestions why this happens?
Using version 220.127.116.11.