It would be better than ANY for starters because "any" does not mean "all". (-: * https://news.ycombinator.com/item?id=14720919 https://news.ycombinator.com/i

It would be better than ANY for starters because "any" does not mean "all". (-: * https://news.ycombinator.com/item?id=14720919 https://news.ycombinator.com/item?id=14720919 Of course, if we were redesigning the DNS protocol (which for what you want would be necessary, given how questions are structured) I would suggest being far more radical and not structuring things in terms of separate A, AAAA, CNAME, and SRV resource record sets in the first place; but rather in terms of <domain,transport,service> tuples and <priority,weight,address,port> tuples, as getaddrinfo() roughly is. Query goes out with <example.org,tcp,https>, full answer response comes back with a prioritized and weighted set of IPv4 and IPv6 addresses and port numbers (possibly with intermediate domain names, if one wanted to keep that concept in a redesigned protocol, which one possibly would not) all together.