Celebrate National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17


How does Autodiscover works for external clients?

Posted on 2010-09-17
Medium Priority
Last Modified: 2012-05-10

We have an Exchange 2007 server published over internet with a public IP and DNS records. Do we need to register a DNS record for Autodiscover in order to make it available for external clients? If yes, what type of DNS record required?

Question by:imranrft
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
  • 3
  • 2
  • 2
  • +1

Accepted Solution

OrcaKnight earned 128 total points
ID: 33705627
You do need a DNS record, usually a subdomain, for autodiscover.domainname.org, but in order for Exchange to properly get the Autodiscover settings,et al., you need to purchase an SSL certificate with multiple names in it. The cert needs to have your internal domain name, your external domainname if you host a secure website, your email server internal domain name, your external mail domain name, the hostname of the internal email server and the autodiscover. As an Example:


The reason you put in the internal server name is that you use it for authenticating internal Outlook client's easier, and you require it for standard RPC over HTTP proxy.

Author Comment

ID: 33705732
So, a wildcard certificate will be OK?

And how can we buy a certificate with many names in it? I mean, do the certificate providers give us the flexibility to add multiple names?

LVL 58

Assisted Solution

tigermatt earned 248 total points
ID: 33705917

There are two ways to make Autodiscover work.

The first (and most common method) is a DNS A or CNAME record - autodiscover - which maps to the public IP/alias of your outward facing Client Access Server/farm.

The second is to use a DNS SRV resource record to reference the location of the autodiscover services - this is a good workaround to the multi-name certificate requirement, but it causes many, many issues particularly down to the fact many DNS providers do not support SRV records. For a minimal expense, you can upgrade to a SAN/UC certificate and save the hassle of ever needing the SRV record approach.

>> how can we buy a certificate with many names in it? I mean, do the certificate providers give us the flexibility to add multiple names

Most major suppliers offer what is known as a SAN (Subject Alternative Name) - also known as UC (Unified Communications) - certificate. These can have multiple names listed and have a "default" name (the common name) used for any device which does not support the SAN format. The common name should always be your main public OWA/Exchange ActiveSync URL - if a mobile device, for example, cannot read SANs, it is less likely to have SSL issues in this set up.

The SAN names noted above are the general recommendation. You do not NEED internal server names on the certificate (I always set mine up without them, so the certificate is not server dependent). However, using internal names makes it easier and eliminates the hassle of playing with URLs in Exchange Powershell.

GoDaddy, and their many affiliates, offer SAN/UC certificates at an affordable price.

>> a wildcard certificate will be OK

Wildcard certificates work to a point. They will cover your back for autodiscover.domain.com and mail.domain.com. They will not be valid for the internal server and domain names, so some URLs on Virtual Directories might need updating if you don't want Outlook 2007+ showing certificate prompts internally. Also, be aware that Windows Mobile 5 devices did not support wildcard certificates, making it a particular sticking point back then. There may be other devices on the market today in a similar position.

Visualize your virtual and backup environments

Create well-organized and polished visualizations of your virtual and backup environments when planning VMware vSphere, Microsoft Hyper-V or Veeam deployments. It helps you to gain better visibility and valuable business insights.


Expert Comment

ID: 33707790
I would strongly recommend you to read the below Autodiscover Whitepaper as it gives all the options to configure Autodiscover over the Internet and it also explains how to configure the same.

White Paper: Exchange 2007 Autodiscover Service

Assisted Solution

Raghuv earned 124 total points
ID: 33707793
And regards to Wild card certificate, Matt has already explained you about it. Also you can refer to the below article,

Wildcard Certificate Causes Client Connectivity Issues for Outlook Anywhere

Author Comment

ID: 33715468
Thanks for the info guys.

By the way, what is needed to make AutoDiscover work internally in the first place?
LVL 58

Assisted Solution

tigermatt earned 248 total points
ID: 33719841

Autodiscover is a rather complex system, but at a high level you need to ensure the appropriate DNS records are created *and can be accessed* internally.

Also, you must ensure a valid third-party (trusted) SSL certificate is in place on the Exchange Server and that your virtual directory URLs are correct. If the URLs on the VDirs are incorrect, autodiscover will publish incorrect information which will cause issues with the availability service, Out of Office assistant, OAB downloads and many other things.


Author Closing Comment

ID: 33760643
All of you!

Thank you very much for the help..

Featured Post

Office 365 Training for Admins - 7 Day Trial

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

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...
One-stop solution for Exchange Administrators to address all MS Exchange Server issues, which is known by the name of Stellar Exchange Toolkit.
In this video we show how to create a Contact 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 Recipients >> Contact ta…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…

730 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