Il 30 Mar 2004 alle 15:45 Chris Meadors immise in rete
> Nope, the problem is with altavista. Just to sum up what you said
> again:
> $ host altavista.com
> altavista.com has address 209.73.164.90
> $ host -t mx altavista.com
> altavista.com mail is handled by 0 .
no, it say tha MX 0 (maximum priority) is handled by " . "
altavista.it. 4037 IN MX 0 .
of course "." cannot resolve to any host (or all ... it is the whole internet).
A fix could be to accept it as been the A record for the domain, and send
to the A record.
It would be as if it had been:
altavista.it. 4037 IN MX 0
that however is a DNS record illegal.
this could be an interesting notation for example as:
.... MX 20 .
MX 10 mail
that could signify ro use mail.domain as primary mx, but if it is broken
use the A record for the domain as secondary
(there are better way ... but be strict on which you send and be lenient on
what you get !)
> So, altavista.com resolves to an IP. If they didn't have an MX mail
> would be delivered there. But they do advertise an MX, albeit
> invalid, but an MX non-the-less. So mail will be sent there...and
> fail. -- Chris
--
Leonardo Boselli
Nucleo Informatico e Telematico del Dipartimento Ingegneria Civile
Universita` di Firenze , V. S. Marta 3 - I-50139 Firenze
tel +39 0554796431 cell +39 3488605348 fax +39 055495333
http://www.dicea.unifi.it/~leo
