Jon's absolutely right. Each MX record has a "Priority" and that is the order that they should be contacted. For example, my company's MX records (from http://www.zoneedit.com/lookup.html?host=davidclark.com&type=MX&server=&; forward=Look+it+up) are: davidclark.com MX 10 mail.davidclark.com. davidclark.com MX 20 backup-mx.choiceone.net. The first one is my mail server. The second in the ISP's "Backspooler" mail server, that will, when configured properly, receive and queue mail for my domain. One important note: while the RFC says that mail senders should contact the mail servers in order, that does not always happen. For example, many spammers will intentionally target secondary MX servers, because most people tell their spam software to pass-on unmolested the mail that their backup MX servers relay. For this reason, either make sure that there is a compatible spam detection system running on the backup server (unlikely...) or make sure that all mail that comes from the backup server also has to pass through some Spam software on its way in. HTH, Glenn Sullivan, MCSE+I MCDBA David Clark Company Inc. ________________________________ From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Ray Costanzo Posted At: Thursday, January 10, 2008 8:45 AM Posted To: Windows 2000 Conversation: [windows2000] Re: MX records question Subject: [windows2000] Re: MX records question If this what happens, this would be rather ideal for my needs. Thanks Jon! I'm off to do some testing. From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Jon Spriggs Sent: Thursday, January 10, 2008 3:27 AM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] Re: MX records question If I remember rightly, MX records have a priority, so it'll try priority 1 server first (1.2.3.4), then if it can't reach that, it'll try priority 2 (5.6.7.8 ) and so on. I think the highest priority is 100, but different BIND/DNS servers will have more or less available records, depending on how complex they expect their users to be! It's usually used as follows: Priority 1) Local Office SMTP Server Priority 2) Main Branch SMTP Store-and-forward Priority 3) ISP SMTP Store-and-forward This then means that the default is for it to arrive at your branch office. If for some reason, the downstream mail service can't see your office (you have no power, your mail server coughs or there's just too many connections for your local server to cope with), then it'll try your main branch server. If that's down (same reasons), it'll try the ISP. Rgds, Jon On 1/10/08, Ray Costanzo <ray@xxxxxxxxxx> wrote: Oops. And that second mx record sends mail to 5.6.7.8, or some other destination different from the first record, that is... From: windows2000-bounce@xxxxxxxxxxxxx [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Ray Costanzo Sent: Wednesday, January 09, 2008 10:35 PM To: windows2000@xxxxxxxxxxxxx Subject: [windows2000] MX records question So, here's my question. Let's say I own a domain, raysdomain.com, and I have an mx record published that sends mail to 1.2.3.4. What happens if I publish a second mx record? I notice in my host's dns admin control panel, I can have more than one mx record. I don't want to try it out to see. -- Jon Spriggs LPIC-1 Certified hackerkey.com://v4sw6BHUhw5ln3pr5$ck4ma3u7L$w5TUX$m5l7ADFKLRSU$i852Ne5t5 BGRSb8AGKMOPTen6a2Xs0Ir5p-2.88/0g5CMT ***************************** New Site from The Kenzig Group! Windows Vista Links, list options and info are available at: http://www.VistaPop.com ***************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm