Making the two MX records point to the same IP defeats the entire point.
We want redundancy in our mail services. If one ISP goes down, the other
keeps working, automatically. You must have different IPs on different
networks to do that.

As you say, the important thing is that the mail server respond to incoming
connections on the same IP that is listed. So how do I make that happen
when there are two IPs corresponding to two MX records on two different
ISPs?

--
Will
westes AT earthbroadcast.com


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> "CHANGE USERNAME TO westes" <(E-Mail Removed)> wrote in
> message news:KeOdnaHRvZZIpjfdRVn-(E-Mail Removed)...
> That won't happen. It doesn't need to happen either, it's kind of
pointless
> with a mail server anyway. Outbound traffic is always anonymous between
your
> mail server and the destination mail server. The only important thing is
> that the mail server response to Incomming on the same IP# listed in the
MX
> record. You can also make the mail server look like "two hosts" by having
> both MX records point to the same IP# incomming. Worrying about what IP#
is
> being used in either direction is really the wrong approach.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com

"CHANGE USERNAME TO westes" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> Making the two MX records point to the same IP defeats the entire point.
> We want redundancy in our mail services. If one ISP goes down, the other
> keeps working, automatically. You must have different IPs on different
> networks to do that.

I don't think what you want can be done. The goal is to have a single ISP
that is dependable and can quickly recover from downtime.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com