Some cant resolve my mail server after a recent domain move, while most can.

here's the scenario:  Recently moved a customer's web domain from one provider to another. (ez-web to GoDaddy). Along with the outside website hosted by the provider, we are running an SBS2003 Exchange Server with the MX record for this domain pointing to the IP address of the company's firewall and exchange server at a different location.  When the domain was moved, the MX records were apparently reset to GoDaddy's internal email servers temporarily (about 2-3 hrs) before I became aware, and went into their interface and updated the MX and A records back to the IP and host of the mail server, not the webhost. Within 5 minutes after that, mail was incoming again and working.  However, since this move several customers report they cannot send email to us anymore, and have forwarded a variety of errors for me to try and correct on my end. I contacted GoDaddy and they say my MX and other DNS records are all set up properly, and confirmed they were working.  

here's one of the errors..which points to the incorrect mail servers... the domains and email addys are obscured here.

--- Session Transcript ---
 Fri 2008-06-13 11:11:57: Parsing message
<xxxxxxxxxxxxxxxxxx\pd50000321100.msg>
 Fri 2008-06-13 11:11:57: *  From: customer
 Fri 2008-06-13 11:11:57: *  To: enduser@mydomain.com
 Fri 2008-06-13 11:11:57: *  Subject: TEST
 Fri 2008-06-13 11:11:57: *  Message-ID:
 Fri 2008-06-13 11:11:57: Attempting SMTP connection to
[mydomain.com]
 Fri 2008-06-13 11:11:57: Resolving MX records for [mydomain.com]
(DNS
Server: 12.127.16.68)...
 Fri 2008-06-13 11:11:57: *  P=000 S=001 D=mydomain.com TTL=(50)
MX=[smtp.secureserver.net]
 Fri 2008-06-13 11:11:57: *  P=010 S=000 D=mydomain.com TTL=(50)
MX=[mailstore1.secureserver.net] {64.202.166.11}
 Fri 2008-06-13 11:11:57: Attempting SMTP connection to
[smtp.secureserver.net:25]
 Fri 2008-06-13 11:11:57: Resolving A record for [smtp.secureserver.net]
(DNS Server: 12.127.16.68)...
 Fri 2008-06-13 11:11:57: *  D=smtp.where.secureserver.net TTL=(4)
A=[64.202.166.12]
 Fri 2008-06-13 11:11:57: Attempting SMTP connection to
[64.202.166.12:25]
 Fri 2008-06-13 11:11:57: Waiting for socket connection...
 Fri 2008-06-13 11:11:57: *  Connection established (192.168.0.99:1616
->
64.202.166.12:25)
 Fri 2008-06-13 11:11:57: Waiting for protocol to start...
 Fri 2008-06-13 11:11:57: <-- 220
pre-smtp21-02.prod.mesa1.secureserver.net
ESMTP
 Fri 2008-06-13 11:11:57: --> HELO .com
 Fri 2008-06-13 11:11:57: <-- 250
pre-smtp21-02.prod.mesa1.secureserver.net
 Fri 2008-06-13 11:11:57: --> MAIL From:<customer>
 Fri 2008-06-13 11:11:58: <-- 250 ok
 Fri 2008-06-13 11:11:58: --> RCPT To:<enduser>
 Fri 2008-06-13 11:11:58: <-- 553 sorry, relaying denied from your
location
[63.173.109.60] (#5.7.1)
 Fri 2008-06-13 11:11:58: --> QUIT

=====================================================
here's another one..

-----Original Message-----
From: mailer-daemon@maxmail021.maximumasp.com
[mailto:mailer-daemon@maxmail021.maximumasp.com]
Sent: Tuesday, June 17, 2008 8:47 AM
Subject: Undeliverable: RE: PURCHASE

Your message did not reach some or all of the intended recipients.

   Sent: Tue, 17 Jun 2008 08:59:06 -0400
   Subject: RE: PURCHASE

The following recipient(s) could not be reached:

myuser@mydomain.com
   Error Type: SMTP
   Error Description: No mail server
   Additional information: No mail servers exists for the address.

hMailServer
 =======================================================
And the First one to report an issue, this error:

Subject: Delivery failure notification


With reference to your message with the subject:
   "Internet Messages"

The local mail transport system has reported the following problems it encountered while trying to deliver your message:

-------------------------------------------------------------------
*** user@mydomain.com
Error connecting to primary server '68.178.232.100'.

=========================================================

Anything I can point these people to that will help them get more accurate DNS data and/or get them resolving this domain handled by Godaddy ??.. this last customer example tried to email me at another domain also handled by GoDaddy and it also did not get through, but did to another outside domain not associated to that provider..so in this case, it doesnt appear to be the destination mail server at all so much as the source sender having trouble resolving anything past godaddy name servers...   but all of the 3 cases now in front of me occurred just after this domain was moved and hasnt worked itself out in the last 4-5 days now.

Help !!  

Start Free Trial