29 messages in net.sourceforge.lists.courier-usersRe: [courier-users] MX randomizing: t...
FromSent OnAttachments
Rodrigo SeveroJun 22, 2005 1:28 pm 
Sam VarshavchikJun 22, 2005 2:05 pm 
Rodrigo SeveroJun 23, 2005 2:32 am 
ArnoJun 23, 2005 4:06 am 
Rodrigo SeveroJun 23, 2005 5:12 am 
Sam VarshavchikJun 23, 2005 6:06 am 
Rodrigo SeveroJun 23, 2005 6:24 am 
Sam VarshavchikJun 23, 2005 6:58 am 
Ben KennedyJun 23, 2005 7:07 am 
Sam VarshavchikJun 23, 2005 7:26 am 
Gordon MessmerJun 23, 2005 8:39 am 
Rodrigo SeveroJun 23, 2005 1:06 pm 
Alessandro VeselyJun 24, 2005 12:04 am 
Rodrigo SeveroJun 24, 2005 4:32 am 
Scott MorizotJun 24, 2005 5:31 am 
Sam VarshavchikJun 24, 2005 6:00 am 
Rodrigo SeveroJun 24, 2005 6:43 am 
Sam VarshavchikJun 24, 2005 7:06 am 
Scott MorizotJun 24, 2005 7:13 am 
Rodrigo SeveroJun 24, 2005 8:02 am 
Gordon MessmerJun 24, 2005 8:21 am 
Gordon MessmerJun 24, 2005 8:26 am 
Rodrigo SeveroJun 24, 2005 8:50 am 
Scott MorizotJun 24, 2005 9:48 am 
Sam VarshavchikJun 24, 2005 10:33 am 
Rodrigo SeveroJun 24, 2005 10:41 am 
Alessandro VeselyJun 25, 2005 9:29 am 
Rodrigo SeveroJun 26, 2005 7:35 am 
Rodrigo SeveroJun 26, 2005 9:08 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] MX randomizing: trying to understand thesources.Actions...
From:Rodrigo Severo (rodr@fabricadeideias.com)
Date:Jun 24, 2005 4:32:14 am
List:net.sourceforge.lists.courier-users

Alessandro Vesely wrote:

Sam Varshavchik wrote:

A real DNS server returns records in random order. That's a fundamental function of DNS: load balancing.

Is it random or round robin?

I've checked bind9's documentation, it's random-cyclic as they call it, i.e., they just randomly choose the new first member of the list and then recreate the list in the same order from this point.

As far as I can understand this would result in much less than reasonable load balancing for MX records.

I still couldn't get a comment from Sam on this matter but I really think that Courier's current strategy for MX choosing isn't very reasonable as it relies on the randomness of the list provided by bind. It's fast but rather uneffective.