----- Original Message ----- From: "Colbeck, Andrew" <[EMAIL PROTECTED]>
> On various domains I administer, a single point of failure mailhost has been > good enough, but I'm shortly going to add a second host on a second network > for redundancy. > > Now, I understand *how* to do that, but what I would like to hear from those > who've been there before me is *what* you preferred to implement, whether > you choose to talk about bandwidth, administrivia, or spam control. > > For example I could keep my single MX record and have round robin on the A > records. Or I could make a separate MX record and A record for each > mailhost, or do a classic MX = 10 and MX = 20 with a separate A record for > each. I would go with two MX hosts of equal preference: example.com MX 10 gw1.example.com example.com MX 10 gw2.example.com gw1.example.com A xxx.xxx.xxx.xxx gw2.example.com A yyy.yyy.yyy.yyy Then you can easily change the preferences if you need to, or add gateways at the same preference. This is a nice way to balance the load across all of you mail exchangers, and if one drops out of services for some reason, no sweat, since sending mail servers will simply try the next one. This is exactly how we have our gateways setup, and it allows us to drop them in and out of service for maintenance whenever necessary without disrupting anything. My two cents... Bill --- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)] --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
