If your client recieves multiple A/AAAA resource records, your client has no way to know what order they should best be tried in, from the server's point of vie

If your client recieves multiple A/AAAA resource records, your client has no way to know what order they should best be tried in, from the server's point of view, and there is no way for the content DNS server to transmit that information. * http://jdebp.eu./FGA/dns-round-robin-is-useless.html http://jdebp.eu./FGA/dns-round-robin-is-useless.html Note that making priority and weighting available is given in the rationale section of the original RFC from 1996. What you're talking about actually isn't specific to HTTP. * https://tools.ietf.org/html/rfc2052 https://tools.ietf.org/html/rfc2052