Aaron S. Joyner wrote:
Unless I missed it in the thread some where, you haven't said what
domain you're actually checking up on, so it's hard to know if the
above output is correct. Hypothetically, if your MX record points to
mail.example.com but you connect to that server and it says it's
spunkymail-a5.dreamhost.com, you should change your MX record so that
it says your pointing to spunkymail-a5.dreamhost.com. That's roughly
what the original message was complaining about, if my understanding
is correct. As the message said though, it's just a warning, and
isn't at all uncommon to have an MX record pointing to the A record
"mail.example.com", which is in fact something like
captnkirk.example.com, and responds as such in its connection
greeting. Whether you can control it or not, wether you choose to
change your MX or not, this one isn't worth loosing any sleep over.
Ok :) I'm just dealing with a "concerned" client who wants to know why
everything from dnsreport.com isn't coming up roses.
original domain checking: authentic-alternatives.com
(mail.authentic-alternatives.com)
reply from telnet: 220 spunkymail-a5.dreamhost.com ESMTP
I think I'm just going to try and fluff this one off. Like you say - no
reason in losing sleep :)
Lisa B.
--
TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ : http://trilug.org/faq/
TriLUG Member Services FAQ : http://members.trilug.org/services_faq/
