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$i852Ne5t5BGRSb8AGKMOPTen6a2Xs0Ir5p- 2.88/0g5CMT