MX points to different sub-domain than Exchange receive connector - it works - why?

Hi,

This may be a silly question, but I want to know why my setup works when a hint of some perhaps common sense tells me it probably shouldn't.

Setup is SBS 2011 with Exchange where my domain and website is hosted externally.

My MX records point to mail.mydomain.com. I have an A record that points mail.mydomain.com to my ip of my server.

That all seems fine and I guess that's all it needs to work, but my receive connectors in exchange on the first tab that says "Specify the FQDN this connector will provide in response to HELO or EHLO:" is remote.mydomain.com.

I assume that last bit should be mail.mydomain.com, but what will changing it do for me? More, less or nothing?

Many thanks, Warren
Warren_RAsked:
Who is Participating?
 
cfletch1980Connect With a Mentor Commented:
Changing it will not do nothing for you except as it says the FQDN response provided when it receives a EHLO or HELO. I am sure if you look on the network tab the IP address of your SBS server is listed as a server that can receive email. Thats what really matters

On my SBS 2011 server my local server name is listed as it should be by default. The remote.yourdomain.com works for active sync as that is configured during the setup and you can verify selecting Client Access Server in the EMC and the looking at properties for Active Sync. It probably has https://remote.yourdomain.com/...

SBS 2011 is slick as even with external hosted domain during the setup if you allow setup to, it will connect to your hosting partner and configure DNS records for you.

Hope this helps
0
 
Warren_RAuthor Commented:
Also, the iphones use remote.mydomain.com as their server in the Exchange account settings.
0
 
R. Andrew KoffronConnect With a Mentor Commented:
that sounds fine. just make another A record that points remote.mydomain.com to your server's IP also.
you can have multiple A records pointing at the same address.
0
 
FarWestConnect With a Mentor Commented:
it will work, but some smtp hops will treat it as unauthorized MX, and refuse to deliver message (i.e. disconnect the session), others will go on and complete the smtp sessions
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.