Why would you think that it doesn't matter that the traffic doesn't match the ratios I picked? I picked them for a reason.
Why would you think that it doesn't matter that the traffic doesn't match the ratios I picked? I picked them for a reason.
People without cached records will always get the returned servers with the lowest load.
I was referring to load balancing and not splitting traffic for an experiment.
Then, if you return both IPs, you're very likely to eventually come across some people who sort multiple returned A/AAAA records and will prefer one that's "closer" to their current IP. Because if you're in 1.0.0.0/8, it's certainly going to be better to connect to 1.2.3.4 instead of 5.6.7.8. Same thing happens in v6 land, of course.
Lumpy results just means the times for an IP to be rotated out will be lumpy, and not that the server load will be lumpy.
>That's possible, but not always available.
If you build it, then it's always available.
There are many of DNS services which offer an API for querying and updating records.
It is very easy to write a service / script that just fines the X least loaded servers and then call an API to set those as the available records. In practice you will also want to implement some monitoring that it is actually working.