Setting up MX record properly

[BCC1Tech]

Hello. I'm having trouble with an MX record. I had it setup and all but one domain could send to us. I had it setup with the MX record pointing to our static ip address.

I have one domain that is unable to send to us with the setup above, so I changed the setup to create an A record and point the MX to the A record. I'm not sure what the A record should be. I assumed is should be remote. since that is what our web access is.

Our web access is remote.domain.com/owa, so I'm not sure how to set it up properly. Below is what I have setup at GoDaddy:

ARecord @ OUR STATIC ADDRESS
ARecord remote OUR STATIC ADDRESS
ARecord ftp1 OUR STATIC ADDRESS
CNAME

http://www @

CNAME ftp @
MX @ OUR STATIC ADDRESS (priority 0) (I still have this setup because I'm afraid to delete it)
MX @ remote (priority 10)

ANY HELP WOULD BE GREAT!!!

 

[ShackDaddy]

The only one you need is your MX that points to REMOTE. You don't want to have the one pointed to your IP. MX records are always supposed to point to A-records, not to IP addresses.

If everyone was able to email you except one domain, that means your MX record is working fine. Something else is causing the problem for that domain. The MX record is NOT the problem.

If someone in that domain is able to run NSLookup on their mailserver and query the MX record for your domain, they will be able to tell where they are trying to send your mail, and if it's not to 'remote.yourcompany.com', that explains the problem. Or it could be that your server is actually blocking their mail due to some other reason.

Dave Shackelford
ThirdTier.net

 

[BCC1Tech]

Dave -

Thank you for your reply. The mistake I made was I didn't put in remote.domain.com. I thought it was like an A record and I just needed to put the prefix in. When I put in the full remote.domain.com into the MX record, it was fixed.

Thanks for your response!