RedDoorSupplies
asked on
Exchange 2013 additional domains
Hi I have just taken over a server running Exchange 2013 which is the first time I have used it.
They have got a few different domains spread over a few different users which accept emails fine.
I have purchased a new domain and set the MX record to the IP address of the Exchange 2013 server.
I have added the new domain into the accepted domains and looks to be setup the same as the others.
I have then attached a new email address to a user and send a test but nothing is received.
If I send an email to the old address it works fine.
Have I missed something on the server when adding the domain?
Thanks
They have got a few different domains spread over a few different users which accept emails fine.
I have purchased a new domain and set the MX record to the IP address of the Exchange 2013 server.
I have added the new domain into the accepted domains and looks to be setup the same as the others.
I have then attached a new email address to a user and send a test but nothing is received.
If I send an email to the old address it works fine.
Have I missed something on the server when adding the domain?
Thanks
Can you confirm that the MX records are pointing to the same place as the other domains in your environment?
ASKER
Hi yes MX records are the same as far as I can see.
We don't own the old domains so they will be phased out.
Only difference I can see is the MX record is mail.olddomain.com but I have setup remote.newdomain.com
They both point to the same IP address.
That's what's making me think it's a setting in Exchange 2013 I have missed.
Thanks.
We don't own the old domains so they will be phased out.
Only difference I can see is the MX record is mail.olddomain.com but I have setup remote.newdomain.com
They both point to the same IP address.
That's what's making me think it's a setting in Exchange 2013 I have missed.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Excellent :)
ASKER
Was down to a DNS propagation issue
ASKER