On Wed, Mar 07, 2001 at 08:01:29PM +0300, Alex Povolotsky wrote:
> On Wed, Mar 07, 2001 at 08:36:58AM -0800, Greg White wrote:
> > It seems to me that qmail will only try the other MXs if it cannot
> > _connect_ to the MX it tries -- an opened but failed connection means
> > that it will continue to try the best-preference MX (similar to multiple
> > DNS servers in /etc/resolv.conf). Masters of the qmail Source (tm) can
> Well... I see it...
>
> But:
>
> nslookup mx.port.ru
> Server: localhost.2sun.ru
> Address: 127.0.0.1
>
> Non-authoritative answer:
> Name: mx.port.ru
> Addresses: 194.67.23.42, 194.67.23.46, 194.67.23.32, 194.67.23.33
> 194.67.23.37, 194.67.23.40
>
I may have to take back what I said about the MX records -- I cannot get
any ns for mail.ru to tell me anything but mx.port.ru for the MX record
for mail.ru. It appears they're trying to load-balance based on
round-robin DNS (which strikes me as silly for MX records in most cases)
with a large (for round-robin -- 12H) TTL. That kinda defeats the
purpose of round-robin, no? So mx.port.ru is broken (IMHO) in more than
one way....
If the OP's MX record information was correct, my advice would have
been correct. Given what I see now, for at _least_ twelve hours, qmail
will keep trying the IP address that the local resolver has in its cache
for mx.port.ru, and the only way to get mail to deliver to this domain
would be (and feel free to correct me on this) to flush the cache of the
local resolver and hope that it caches a different A record.
--
Greg White
Those who make peaceful revolution impossible will make violent
revolution inevitable.
-- John F. Kennedy
