Chris Angelico wrote:
few months. It's not a simple fix. The default behaviour of Protocols.DNS.async_host_to_ip, which is used by Protocols.HTTP, changed from "only look up A records" to "look up AAAA and A records, and return the first AAAA if found, otherwise the first A".
In accordance to the rule that if a connection over IPv6 is possible, it should be preferred.
Unfortunately everything is built to assume that there's at most one IP address for that host name.
I'd say, the way forward should be changing the connecting functions to iterate through the IP addresses and find the first that actually connects.
Needn't revert completely. If it's decided that the preference should continue to be A, then it's just a matter of reversing the order of returned values - a simple matter of switching two numbers.
That would be an acceptable workaround until the connection code is fixed, I think.