<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Benjamin Smith wrote:
<blockquote cite="mid200510251648.16427.lists@benjamindsmith.com"
type="cite">
<pre wrap="">Using multiple A records is good for performance balancing, but what if one of
the systems fails?
Using your cocnfiguration, the delivering mail server has an "a" record and a
single MX, so it wouldn't try the other mail server in the case of a failure,
right?
Whereas, by listing multiple IPs and mx1/mx2, wouldn't the delivering mail
server try the other address?
Thanks,
-Ben
On Tuesday 25 October 2005 16:02, you wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I once did this and it worked great:
IN MX 10 mx.example.com.
mx IN A 192.168.1.1
IN A 192.168.1.2
...etc. Perfect DNS load balancing.
Jack
Benjamin Smith wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Currently, we have two mail relays for inbound messages, and a third for
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->POP.
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">The inbound messages go thru all the CPU-intensive anti-spam stuff, and
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->then
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">they relay it to the POP server for pickup.
Currently, one of these is the "primary", and the other is "secondary", and
I'd like them to be considered more or less as equals, since the "primary"
system is getting beaten pretty hard.
The DNS zone file says something like this:
###############################
@isp.com
<SNIP>
IN MX 100 mx1.isp.com.
IN MX 1100 mx2.isp.com.
<SNIP
################################
I seem to recall that I make them act as "equals" by simply changing this
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->to
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">###############################
@isp.com
<SNIP>
IN MX 100 mx1.isp.com.
IN MX 100 mx2.isp.com.
<SNIP
################################
so that they both get about the same amount of inbound messages. Has
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->anybody
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">here actually done this? How well does this work as far as failover if
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->either
</pre>
<blockquote type="cite">
<blockquote type="cite">
<pre wrap="">system fails?
-Ben
--
"The best way to predict the future is to invent it."
- XEROX PARC slogan, circa 1978
_______________________________________________
CentOS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:CentOS@centos.org">CentOS@centos.org</a>
<a class="moz-txt-link-freetext" href="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</a>
</pre>
</blockquote>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
In addition to the entire Cyrus system, we have 3 MX records. All are
set to 0 with the exception of the lists server, which is set to 10.<br>
<br>
--<br>
Nathaniel Hall, GSEC<br>
</body>
</html>