https://bugs.winehq.org/show_bug.cgi?id=46704
--- Comment #34 from Hans Leidekker hans@meelstraat.net --- Good run:
0066:trace:winsock:WS_getaddrinfo "auth.riotgames.com", "443" 0x48cf518 -> 0xad0fe50 0 0066:trace:winsock:WS_inet_ntop family 2, addr (0x490a0a4), buffer (0xad0fdde), len 16 0066:trace:winsock:WS_getaddrinfo => 0x48dfd50, flags 0, family 2, type 1, protocol 0, len 16, name (null), addr { family AF_INET, address 104.16.120.50, port 443 } 0066:trace:winsock:WS_inet_ntop family 2, addr (0x490a0e4), buffer (0xad0fdde), len 16 0066:trace:winsock:WS_getaddrinfo => 0x490a0b8, flags 0, family 2, type 1, protocol 0, len 16, name (null), addr { family AF_INET, address 104.16.119.50, port 443 }
Bad run:
0066:trace:winsock:WS_getaddrinfo "auth.riotgames.com", "443" 0x48cfcc8 -> 0xad0fe50 0 0066:trace:winsock:WS_inet_ntop family 2, addr (0x48e1a54), buffer (0xad0fdde), len 16 0066:trace:winsock:WS_getaddrinfo => 0x48f2640, flags 0, family 2, type 1, protocol 0, len 16, name (null), addr { family AF_INET, address 104.16.119.50, port 443 } 0066:trace:winsock:WS_inet_ntop family 2, addr (0x48f0d0c), buffer (0xad0fdde), len 16 0066:trace:winsock:WS_getaddrinfo => 0x48f2820, flags 0, family 2, type 1, protocol 0, len 16, name (null), addr { family AF_INET, address 104.16.120.50, port 443 }
So the 2 addresses are returned in different order. You'd need to do some more runs to see if one of these consistently fails. If I look up the hostname manually on Debian 9 (dig auth.riotgames.com) I get a seemingly random order of the A records. On Windows the order is strictly reversed every time I look it up (nslookup auth.riotgames.com).
Another interesting bit is that the TTL for auth.riotgames.com (CNAME record for auth.riotgames.com.cdn.cloudflare.com) is dynamic. The 2 A records also have a dynamic TTL. The A record TTL values are always the same, but different from the CNAME TTL.