shane> I wrote a quick draft to specify that answers returned should be shane> returned in a random order:
While it seems like a good idea to have the auth shuffle, my experience from doing tech support for BIND and having this conversation way too often is: - there are way too many moving parts between auth server and client app to have any use trying to dictate RR order - the folks that care about one address hitting too often usually have far more leverage with app developers than with all the said moving parts in between (public recursives, enterprise recursives, load balancers, systemd, OS, stub resolvers, etc.) If you look at those two issues, it becomes more and more obvious that getting the apps to randomize order is going to be far faster to get implemented, far more effective/consistent, and much less non-deterministic than pushing the wet string by randomizing auth answers. _______________________________________________ DNSOP mailing list -- dnsop@ietf.org To unsubscribe send an email to dnsop-le...@ietf.org
