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:Alessandro Vesely (ves@tana.it)
Date:Jun 24, 2005 12:04:47 am
List:net.sourceforge.lists.courier-users

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?

For multihoming, load balancing should imply that querying from net A results in (at least averagely) different addresses than querying from net B. Then, even when I get the same address as the previous connection, I cannot be sure that using it I will connect to the same host. (E.g. Load balancing with reverse NAT.) Such features make it difficult to mark a host as BAD...