Solved

Exchange 2013 Autodiscover and redundancy and an IP question

Posted on 2016-08-24
6
42 Views
Last Modified: 2016-08-26
I am configuring Exchange 2013 but I have not been able to find documentation on the Autodiscover DNS record. If autodiscover points to the mailserver, and that mailserver goes down, how does it know where to fail over to? Do I need a second Autodiscover record? in the same vein, how many public IP addresses do I need for Exchange 2013? Is it one to handle Autodiscover requests and one for everything else? or can everything be done over port 443 on a single IP address? is there a way to split this out, asking because it appears that our old 2010 infrastructure achieved this (and I don't like it!).
Thanks!
0
Comment
Question by:it_medcomp
  • 3
  • 2
6 Comments
 
LVL 15

Assisted Solution

by:Ivan
Ivan earned 250 total points
ID: 41769443
Hi,

for Exchange 2013 you need min. one ip address, for all DNS records, and that is the usual setup.
You just NAT port 443 to Exchange, and that is it.
Records you need are as below:
1. A record for autodiscover.domain.com
2. A record for everything else, usually mail.domain.com or webmail.domain.com
3. MX record

Redundancy is achieved by using load balancer's (for CAS) or using DAG for MBX. All of this can be behind one public ip address. You just need minimum 2 Exchange 2013 servers and load balancer.

Regards,
Ivan.
0
 
LVL 1

Author Comment

by:it_medcomp
ID: 41770354
That's what I thought, but here is the part I don't understand. Let's say Autodiscover resolves to 123.231.222.111, which happens to be a public IP that the firewall redirects to an internal address 10.10.32.1. 10.10.32.1 goes down. That means effectively that the IP Autodiscover resolves to, 123.231.222.111, becomes unresponsive. How do clients know about the other exchange servers at 10.10.32.2 and 10.10.33.1? This assumes the second site is behind the same firewall as the primary site.

I guess it maps out like this:
Server                                          Public                                         Private
EXCHANGESITE1-1                    123.231.222.111:443               10.10.32.1
EXCHANGESITE1-2                                                                        10.10.32.2
EXCHANGESITE2-1                                                                        10.10.33.1

So the Autodiscover record points mail.contoso.com to 123.231.222.111- With DNSRR as our 'load balancing' strategy, what tells Autodiscover to look at another Exchange server- I don't believe our firewall cares about our internal DNS, and the address is NATted to the IP of the first server.
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 41770545
DNS does not have any redundancy. It has no knowledge that a host is available or not.
If you want to have redundancy then you will need a load balancer to connect the clients to, which will be host aware.

You can give each Exchange server an external IP address and add them to the DNS record. However that will not give you redundancy either. It will be pot luck If a user hits a server that is live or not.
0
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 1

Author Comment

by:it_medcomp
ID: 41770553
OK, so on a similar vein, if I have three sites, A, B and C, and I sit down at A and configure my Outlook client, and sit there for two months, then I go to site B and sit there for a week and then spend a week at C, does Exchange use the AD Site to determine which mailserver I connect to, or is this determined some other way? If so, how do I configure site affinity for Site D, which should use site B's server, assuming the latency is lowest between those two sites than of D to C or of D to A?
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 250 total points
ID: 41770590
Autodiscover is AD site aware.
Therefore if you have servers in three different locations then you can have three different URLs so the traffic goes to the closest server.

However the server the traffic actually hits depends on the version of Exchange.
This subject has been dealt with in some depth on the Exchange team blog.
https://blogs.technet.microsoft.com/exchange/2013/01/25/exchange-2013-client-access-server-role/

I would suggest that you start there.
0
 
LVL 1

Author Closing Comment

by:it_medcomp
ID: 41772370
There were two questions here and they were both answered. Thanks to all who contributed!
0

Featured Post

What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

Join & Write a Comment

Suggested Solutions

Utilizing an array to gracefully append to a list of EmailAddresses
Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
This Experts Exchange video Micro Tutorial shows how to tell Microsoft Office that a word is NOT spelled correctly. Microsoft Office has a built-in, main dictionary that is shared by Office apps, including Excel, Outlook, PowerPoint, and Word. When …

705 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

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now