Sam Varshavchik wrote:
The DNS server already returns DNS records in random order.
I believe that by "random order" you mean a different random order for
each query. If this is the case I would like to ask to which DNS servers
do you refer specifically?
I have two different DNS servers running in my machines that I can
promptly test: DJB's dnscache and glibc's nscd.
Neither one of them returns MX records in a different random order for
each query. As far as as I can tell both of them returns consistently
the same answer until the ttl of the DNS query expires. Then they will
query again and might come up with a new answer, i.e. in a different
order, which will again persist until their ttl expires and so on.
Sam, if I understanding correctly Courier's method to choose which MX to
connect to, it would be correctly described as:
Courier tries to contact MXs in exactly the order returned by the DNS
server. Courier expects that DNS servers's answers came in a different,
random, order for each query.
If this description is right, and if my observations about dnscache and
nscd are right, which I believe all three are, we get to the final
description of how Courier is behaving in my servers:
Couriers tries to contact MXs in exactly the same order returned by DNS
servers until this DNS query expires.
As far as my logs indicate, this is exactly what's happening.
Could you please advise on how can I get a more random MX choosing by
Courier?
Thanks again for your continued patience and support,
Rodrigo Severo
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
courier-users mailing list
courier-users@lists.sourceforge.net
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
