Will this dns config work?

[MJNSBF]

Hello,

I am in the middle of configuring a brand new exchange 2003 server for my company. We previously just had basic pop3 server. Our current pop3 server is mail.mydomain.com and my new exchange box is mail2.mydomain.com

Before I came onboard, the one who configured the pop3 server had users give out the @mail.mydomain.com address instead of @mydomain.com....and now users (boss included) want to continue using this @mail.mydomain.com for the few people who still send mail to them using this. (I've tried getting them to just get rid of it and alert all contacts, but they don't want to do that)

My question is this. With the exchange server, in AD and everything the name of the server is mail2. If I add in the Recipients policy the @mail.mydomain.com address (and check 'this exchange organization is responsible for all delivery to this email address'), and then if I give the new server the ip address of the old mail server, do you think users would be able to receive their mail at both the @mail.mydomain.com and the @mydomain.com addresses?

I'm sorry if this is confusing or unclear. Thanks in advance for any insight.

MJ

 

[wallst32]

As long as both domains are in the recipient policy, and you have MX records that forward mail to this server, and mailboxes have SMTP aliases for both, then you should be fine.

Just keep in mind that the address people see is the primary SMTP address. For example if I have joe@mail.mydomain.com and joe@mydomain.com; and "mydomain.com" is primary for my account, whenever I send outgoing email, it appears to be from joe@mydomain.com.

So somebody could e-mail me at joe@mail.mydomain.com, but my response will come from joe@mydomain.com.

 

[jpm121]

The good thing about what wallst32 mentioned is that eventually (like maybe a couple years) you can be rid of the mail.xx.tld addresses, as people realize that the new @xx.tld addresses work just as well.

 

[rko9h]

What if you have two e-mail servers, say server1.mydomain.com and server2.mydomain.com and one MX record pointing to server1?

- Navy LT

 

[MJNSBF]

Thank you wallst32 for the info! I was hoping that would be the case. jpm121, I was also hoping we could (eventually) rid the mail.xx.tld address!

rko9h, I had thought about that, but we don't want to leave the old server up and running.


-MJ

 

[rko9h]

My previous post wasn't clear. I'm in a similar situation where we are migrating from one server to a new one and will ultimately decomission the old one. For the short time when both servers are up and running, are multiple MX records required?

Right now, I can't get the two mail servers to exchange e-mails. Also, mail sent to mydomain.com bounces if the mailbox is on the newly added server. Thanks.

- Navy LT

 

[MJNSBF]

Hmmmm,

might have run into some problems. Anyone know if I will have certificate issues? For example, during config, we issued certificate ourselves for mail2.mydomain.com. When I switch over, I was going to give it a different ip (one of mail1.mydomain.com)

will that cause an issue if the certificate is for mail2.mydomain.com, but the server doesn't resolve to mail2 anymore?

I'll get it yet.

Thanks in advance.

MJ

 

[MJNSBF]

rko9h,

don't know if you'll see this or not, but we just implemented our new exchange server last week, and we have both server1.mydomain.com and server2.mydomain.com both pointing to the same ip address. It works like a charm!

MJ