Open stefvandessel opened 9 years ago
Will this problem be solved in the future? I still have the same problem with version 4.8.4.
There has not been any interest in this feature since the initial report, as far as I'm aware. Contributing a pull request that implements the shuffling would go a long way, of course. It would probably have to be optional since most users want the packet-cache to be as fast as possible and do not care about the order of records inside a RRset.
I really hope PowerDNS supports this feature
in our environment, we have a degraded case of a minimal number of recursors serving a large number of clients. Setups using DNS round-robin do not work really round-robin in this case because the packetcache will return the answers in the same order most of the time. While DNS round-robin is not really the most preferred way to spread load, it usually works pretty well. (given a large enough userbase using a lot of resolvers)
Current workarounds are to disable the packetcache, or to bypass the packetcache based on the number of A/AAAA records. Both come with a CPU usage increase.
The idea would be to add some type of round-robin in the response to the client so we do not have to do any of the workarounds. Unbound currently has a "rrset-roundrobin" option that does this. Bind does the round-robining by default iirc.