Solved

Exchange 2013 additional domains

Posted on 2014-03-26
6
228 Views
Last Modified: 2014-03-31
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
0
Comment
Question by:RedDoorSupplies
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2
6 Comments
 

Author Comment

by:RedDoorSupplies
ID: 39955797
Also just tried to telnet the new MX record created, so remote.NEWDOMAIN.com and the server responds all ok
0
 
LVL 15

Expert Comment

by:MarkMichael
ID: 39955919
Can you confirm that the MX records are pointing to the same place as the other domains in your environment?
0
 

Author Comment

by:RedDoorSupplies
ID: 39955958
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.
0
PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

 

Accepted Solution

by:
RedDoorSupplies earned 0 total points
ID: 39956150
Hi looks like I may have been a bit quick off the mark and the DNS wasn't fully updated!

Seems ok on one of the new domains now.
0
 
LVL 15

Expert Comment

by:MarkMichael
ID: 39956168
Excellent :)
0
 

Author Closing Comment

by:RedDoorSupplies
ID: 39966137
Was down to a DNS propagation issue
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
This article will help to fix the below errors for MS Exchange Server 2013 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Suggested Courses

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question