3 ms·
If get unlucky A's load will rise quickly and it will no longer have a record for it. As the TTL expires the resolvers will get a new set of servers with low lo
by charcircuit 4y ago
If get unlucky A's load will rise quickly and it will no longer have a record for it. As the TTL expires the resolvers will get a new set of servers with low load.
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.
- toast0 4y agoYou're suggesting that the DNS server(s) get realtime load feedback and adjust appropriately. That's possible, but not always available.
- charcircuit 4y agoYes, that is how you scale DNS load balancing. There is a pretty low limit for the number of records you are allowed to return in practice. Putting 100 A records works with 1.1.1.1, but will break other's resolvers on the internet. >That's possible, but not always available. If you build it, then it's always available.
- toast0 4y agoSure, but a lot of people use other people's DNS services. The number of times I've been allowed to build a DNS service for my employer is zero. I've used static DNS, where you just put in your X number of A records and hope; dynamic services where you put in X and have them serve only Y of them in any request and hope. I've used services with load feedback, but those are always a much higher tier.
- charcircuit 4y ago>Sure, but a lot of people use other people's DNS services 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.