Hey All, I be fishin' for some answers today

OK, have two Exchange 2013 systems hosting both CAS and MBX roles on each server.

Have a DAG set up with both of those servers as members

Before I embarked on this journey to high availability, I had our DNS set up as outlined below:

INTERNAL

• Exch1  192.168.10.100
• autodiscover 192.168.10.100
• mail 192.168.10.100

EXTERNAL

• autodiscover   x.x.x.10
• mail  x.x.x.10

We are utilizing a Cisco IronPort as a Smarthost, located at our ISP

Now, my questions...
With having a second Exchange Server now (EXCH2 - (internal 10.0.4.65 - external x.x.x.20))...
Do I need to have mail.domain.com AND autodiscover.domain.com on our DNS servers with two different IP addresses, or just mail.domain.com?

I'm thinking in the better category it would be both; however, can I get away with just having mail configured twice?

• Edited by Here Fishy Thursday, June 18, 2015 4:13 PM

Both servers are in different AD sites and physical locations.  That is why I have two different IP subnets for the DAG (leased space at COLO have to use their networking design).  Have primary witness server here and alternate configured at COLO (would have preferred a third site; however, do not have one).

Not sure what you mean by disjointed... 
I only want to use the hostnames mail and autodiscover
If my thinking is correct...  I do have  domain.local and domain.com

• Edited by Here Fishy Thursday, June 18, 2015 4:51 PM More info

Yes, I am more or less trying to do a DR at another site.

Exch1 is CAS and MBX
Exch2 is CAS and MBX as well

If Exch1 does down, I want to make sure that Exch1 will jump up to the task for accepting client connections as well as access to the mailboxes

Yes, I am more or less trying to do a DR at another site.

Exch1 is CAS and MBX
Exch2 is CAS and MBX as well

If Exch1 does down, I want to make sure that Exch2 will jump up to the task for accepting client connections as well as access to the mailboxes

• Edited by Here Fishy Thursday, June 25, 2015 3:03 PM

Hi here,

Are Exch1 and Exch2 facing the Internet? If that, when the Exch1 down, Exchange will jump to Exch2 for internal, for external, we should modify MX record in ISP.

If there is a Exch1 site facing Internet and when it down, Exchange will jump to Exch2 for internal, the user who is in external will not connect to Exchange.

If there are any questions regarding this issue, please be free to let me know.

Best Regard,

Jim

That answers my question pretty much...