raptorIT
asked on
Dual Email Domains on 2013 Exchange - need setup assistance.
Hello,
Here is our current configuration,
1 2013 exchange server
2 domains
1 domain which was the original domain setup in exchange can send and receive email
The second domain which was added to the following settings can not send or received. An MX lookup shows the domain is pointed to the right IP
Settings:
Domain Added to accepted domain ( New domain set as default )
default policy edited with new domain ( @domain.com added to default policy)
users email account profile shows both domains
Any ideas, this is a first for us.
Here is our current configuration,
1 2013 exchange server
2 domains
1 domain which was the original domain setup in exchange can send and receive email
The second domain which was added to the following settings can not send or received. An MX lookup shows the domain is pointed to the right IP
Settings:
Domain Added to accepted domain ( New domain set as default )
default policy edited with new domain ( @domain.com added to default policy)
users email account profile shows both domains
Any ideas, this is a first for us.
ASKER
Hi there,
Thank you..correct the ip is but since its different domain of course the host name is different.
for example :
same public IP of course but
companyA@domain1.com
mx mail.domain1.com
not working
companyB@domain2.com
mx.mail.domain2.com
We do not use a spam filter right now, i checked the default hub transport and its set to allow
Thank you..correct the ip is but since its different domain of course the host name is different.
for example :
same public IP of course but
companyA@domain1.com
mx mail.domain1.com
not working
companyB@domain2.com
mx.mail.domain2.com
We do not use a spam filter right now, i checked the default hub transport and its set to allow
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
thank you sir looks to be working now!
ASKER
I guess I was trying to understand the logic of why the other way didn't work if I had a local DNS server with a DNS entry for mail.company2.com and on the Name servers had the mx record pointed to the same IP as company1.com
Most likely you were having issues with something like reverse dns lookup not matching. Many sites now use this as a base authentication to ensure the mail is going to the correct place. A helpful tool for checking is mxtoolbox.com.
If you are going to keep your mail server exposed you may want to look into getting a certificate for it and enable TLS encryption. I suspect more and more sites will soon be rejecting connections that are not encrypted. I have several clients that make it part of the contract if you want to do business with them.
Glad it is working.
If you are going to keep your mail server exposed you may want to look into getting a certificate for it and enable TLS encryption. I suspect more and more sites will soon be rejecting connections that are not encrypted. I have several clients that make it part of the contract if you want to do business with them.
Glad it is working.
ASKER
yes correct we will defiantly use a 3rd party thank you for your help
Don't forget to accept answer and close the thread!
ASKER
works great!
Regarding your MX records, they should be the same as the previous domain. (which still works) The domain names do not need to be reflected in the name of the server handling the mail, the server just needs to accept and work with the mail.