redundancy in fqdn

[crabby117]

We recently forwarded our MX record for email from a remote hosted email service to our own internal Exchange server and are having problems receiving maile (though we can send mail).

When I send an email to myself from an outside source, the delivery error message is immediate and there seems to be a problem with the remote-mta: DNS setting. Whereas it seems that it OUGHT to be either ourdomain.com or mail.ourdomain.com, it's listed as mail.ourdomain.com.ourdomain.com.

I'm not sure if this problem is from an error in our MX record or if it's an internal problem with the Exchange server. When I ping mail.ourdomain.com, it replies with the correct IP of our router. Not sure what's causing the redundancy in the name or how to get rid of it.

Any help would be greatly appreciated.

 

[crabby117]

I've since used a command line and done an nslookup -type=MX on our domain name and it indeed replies with the redundancy.

We resell domains through our host and have a bunch of sub domains. We've gone through this same process with some of our customers having Exchange servers and attempted to do the exact same process for ourselves. One thing I did notice is different, though. For all of our customers, the host lists the "Main MX Record" for all of our subdomains as "mail.theirdomain.com." WITH that extra period after the com. Our domain MX record did not have that extra period at the end. It wasn't something that we ever typed in, it just populated itself. But I could edit the entry and I added the period for our domain. It hasn't made any difference yet, but I'm not sure it will take time to populate across DNS servers.