atom feed34 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: MX lookup
FromSent OnAttachments
Lukas VeselyJul 29, 2002 8:39 am 
Sam VarshavchikJul 29, 2002 2:20 pm 
Lukas VeselyJul 30, 2002 7:59 am 
Sam VarshavchikJul 30, 2002 2:30 pm 
Johannes ErdfeltJul 30, 2002 3:02 pm 
Juha SaarinenJul 30, 2002 3:20 pm 
Sam VarshavchikJul 30, 2002 3:21 pm 
Johannes ErdfeltJul 30, 2002 3:32 pm 
Sam VarshavchikJul 30, 2002 5:35 pm 
Juha SaarinenJul 30, 2002 6:03 pm 
Juha SaarinenJul 30, 2002 6:13 pm 
Johannes ErdfeltJul 30, 2002 6:20 pm 
Johannes ErdfeltJul 30, 2002 6:37 pm 
Sam VarshavchikJul 30, 2002 6:47 pm 
Johannes ErdfeltJul 30, 2002 7:20 pm 
Tabor J. WellsJul 30, 2002 7:31 pm 
Sam VarshavchikJul 30, 2002 7:46 pm 
Juha SaarinenJul 30, 2002 8:05 pm 
Bill MichellJul 31, 2002 1:30 am 
Lukas VeselyJul 31, 2002 6:51 am 
Johannes ErdfeltJul 31, 2002 8:43 am 
Johannes ErdfeltJul 31, 2002 8:48 am 
Ben RosengartJul 31, 2002 9:23 am 
Moshe GurvichJul 31, 2002 9:32 am 
Lukas VeselyJul 31, 2002 9:36 am 
Lukas VeselyJul 31, 2002 9:36 am 
Lukas VeselyJul 31, 2002 9:36 am 
Lukas VeselyJul 31, 2002 9:36 am 
Lukas VeselyJul 31, 2002 10:12 am 
Anand BuddhdevJul 31, 2002 10:17 am 
Johannes ErdfeltJul 31, 2002 10:31 am 
Sam VarshavchikJul 31, 2002 2:41 pm 
Lukas VeselyAug 1, 2002 10:16 am 
Luc BrouardAug 6, 2002 12:34 pm 
Subject:Re: [courier-users] Re: MX lookup
From:Juha Saarinen (ju@saarinen.org)
Date:Jul 30, 2002 6:03:40 pm
List:net.sourceforge.lists.courier-users

On Tue, 30 Jul 2002, Johannes Erdfelt wrote:

I don't think it's that silly.

Multiple NS records, by design, are load balanced. Multiple A records are load balanced.

Why shouldn't multiple MX records be load balanced? What makes them so special to be treated differently?

All you get in either case is a very crude form of loadbalancing. It's not like you'll see: "MX A is quite busy now, try MX B" and so forth all the way down the chain. All RFC 1123 stipulates is that the sending MTA should pick an MX at random, if you have multiple MX RRs with the same preference. So, your MTA might hit busy ones more times than not.

If you want to do that sort of thing, it would probably make more sense to have e.g. four MX with the same preference, and use Round Robin DNS load balancing with A records for the MX'es.

That said, you would've thought that a big, wealthy organisation like Hotmail would be able to use a proper load balancing front-end to their MXes, like UU.NET does.