3 ms·
DNS should perform round-robin in the order of the IPs in the UDP packet. Otherwise you have no control. Just like JSON (and js) hashmaps should really be tree
by bullen 3y ago
DNS should perform round-robin in the order of the IPs in the UDP packet. Otherwise you have no control.
Just like JSON (and js) hashmaps should really be treemaps and retain order.
Last but not least you should be able to make a TCP stream loose order. So you get UDP speed without changing pipes/ports and all that jazz.
It's all about doing that job when you design a protocol.
- teddyh 3y ago> DNS should perform round-robin in the order of the IPs in the UDP packet. That only works if the clients choose the first IP address in the response to connect to. But IPv6, IIUC, specifies that clients instead always use the IPv6 address it has the longest stretch of bits in common with, compared to its own IPv6 address.
- teddyh 3y agoFortunately, there will probably exist, in the somewhat near future, another solution providing simplistic load balancing: HTTPS and SVCB records in the DNS: <https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/ https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https...>
- imtringued 3y agoNobody uses SRV records.