On Tue June 23 2009 06:32:26 Jiří Hlinka wrote:
> Define secodnary MX record for the secondary MDA is one of a
> posiibilities
>
> :-), but i still hope there is simpler solution, something like
> : adding
>
> another IP (the IP of secondary MDA) on each line of transport_maps
> :-).
>
> Im little bit afraid of MX record solution (although it is probably
> the "cleanest" way), because im dont know how much i have to change
> my postfix configuration.
With proper MX records in your own DNS, you don't even need to maintain
the transport_maps. The sloppy way is to use your MX lookup in the
existing transport_maps :
example.com smtp:example.com.your.domain
example.net smtp:example.net.your.domain
example.com.your.domain. MX 10 primary.mda.your.domain.
example.com.your.domain. MX 20 secondary.mda.your.domain.
example.net.your.domain. MX 10 primary.mda.your.domain.
example.net.your.domain. MX 20 secondary.mda.your.domain.
The clean way is to configure your resolver to look at your own DNS
first, before external queries, then do away with transport_maps
altogether:
example.com. MX 10 primary.mda.your.domain.
example.com. MX 20 secondary.mda.your.domain.
example.net. MX 10 primary.mda.your.domain.
example.net. MX 20 secondary.mda.your.domain.
> Please, what do i need to change to go the MX recodrs way? There
> should be MX records specified inside the LAN where prim. and sec.
> MDA are, right? anything other need to be changed?
You'll need to learn how to manage your own DNS software and resolver
client, and that is off-topic for this list. Considering that the
client needs HA, I think it would be an excellent idea to run your own
nameservers. Do the easy things to improve performance before you try
the difficult ones.
--
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
