Pablo Scheri wrote:
dig mx trendargentina.com.ar.
; <<>> DiG 9.3.3rc2 <<>> mx trendargentina.com.ar.
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27701
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2
;; QUESTION SECTION:
;trendargentina.com.ar. IN MX
;; ANSWER SECTION:
trendargentina.com.ar. 0 IN MX 10 mx.trendargentina.com.ar.
;; AUTHORITY SECTION:
trendargentina.com.ar. 0 IN NS imsva.trendargentina.com.ar.
;; ADDITIONAL SECTION:
mx.trendargentina.com.ar. 0 IN A 10.0.0.208
mx.trendargentina.com.ar. 0 IN A 10.0.0.207
What this says to me is every time Postfix requests the MX for
trendargentina.com.ar the name server software will look it up and come
back with _either_ 10.0.0.208 or 10.0.0.207 and depending on how many
other DNS requests are made it might be the same over and over.
If your zone file had
trendargentina.com.ar. 0 IN MX 10 mx1.trendargentina.com.ar.
trendargentina.com.ar. 0 IN MX 10 mx2.trendargentina.com.ar.
...
mx1.trendargentina.com.ar. 0 IN A 10.0.0.208
mx2.trendargentina.com.ar. 0 IN A 10.0.0.207
Then when Postfix asked for the MX record for trendargentina.com.ar the
DNS server would send back the two IP addresses and Postfix would
round-robin/randomize them.
I got the DNS info from readings in "Pro DNS and bind" and the Postfix
from this list and the online documentation.
You implementation has DNS doing the round-robin with the results
depending on how busy the name server is. Mine lets Postfix do it with
a single query to the name server.
As always YMMV. ;-)
Rod
--
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jan 22 16:10:05 2009
;; MSG SIZE rcvd: 110
---------------------------------------------------------
dig a mx.trendargentina.com.ar.
; <<>> DiG 9.3.3rc2 <<>> a mx.trendargentina.com.ar.
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4096
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;mx.trendargentina.com.ar. IN A
;; ANSWER SECTION:
mx.trendargentina.com.ar. 0 IN A 10.0.0.207
mx.trendargentina.com.ar. 0 IN A 10.0.0.208
;; AUTHORITY SECTION:
trendargentina.com.ar. 0 IN NS imsva.trendargentina.com.ar.
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Jan 22 16:10:13 2009
;; MSG SIZE rcvd: 94
--------------------------------------------
postconf | grep dns
disable_dns_lookups = no
lmtp_host_lookup = dns
smtp_host_lookup = dns
-------------------------------------------
grep '10\.0\.0\.20..:25' /var/log/maillog | grep -v status=
No result.
Thanks!
Pablo.-
> Subject: Re: Problems with Postfix / Round-Robin
> To: postfix-users@postfix.org
> Date: Fri, 6 Feb 2009 09:46:43 -0500
> From: wie...@porcupine.org
>
> The DNS looks good. Can you give output for:
>
> $ dig mx trendargentina.com.ar.
> $ dig a mx.trendargentina.com.ar.
> $ postconf | grep dns
>
> The records that result in some kind of error while delivering to
> the mx.trendargentina.com.ar machines. Something like:
>
> $ grep '10\.0\.0\.20..:25' /var/log/maillog | grep -v status=
>
> That's two dots before the ":".
>
> Wietse
------------------------------------------------------------------------
Adminístralas todas usando Windows Live Mail. ¡Descárgalo gratis!
¿Tienes más de una cuenta de correo? <http://download.live.com>
