Configure Autodiscover DNS Records for an Exchange Hybrid Deployment
Question details
Determine whether SRV-based Autodiscover redirection is supported for email domains in an Exchange 2010 to Microsoft 365 hybrid migration.
- Product
- Microsoft Exchange Server 2010 and Microsoft 365
- Device & OS
- not provided
- Scenario
- A hybrid deployment uses a CNAME record for one email domain and SRV records for other domains.
- Observed behavior
- The administrator needs a supported Autodiscover DNS and certificate configuration for each email domain.
List the email domains that need Autodiscover, their current DNS records, and the names covered by the Exchange certificate. Identify the externally accessible Autodiscover endpoint used by your hybrid topology before changing DNS.
Use standard Autodiscover DNS records for each hybrid domain
Replace reliance on SRV-based Autodiscover redirection with standard HTTPS Autodiscover and certificate coverage for each required domain.
For this Exchange hybrid scenario, do not rely on SRV-based Autodiscover redirection. Configure an Autodiscover hostname for each required email domain and direct it to the endpoint appropriate for your hybrid topology.
Exchange Server 2010 is out of support. Review current Microsoft hybrid deployment guidance and plan an upgrade to a supported configuration.
In your DNS provider's management console, review the Autodiscover CNAME and SRV records for each email domain. Record their current targets before making changes.
In the DNS console, create an autodiscover.<domain> CNAME for each required domain, pointing to the Autodiscover endpoint appropriate for your hybrid configuration. Check for conflicting records at the same hostname.
Review the certificate bound to the Exchange HTTPS endpoint and ensure it covers every Autodiscover hostname clients use. Ask your certificate provider about a SAN or UCC certificate if multiple domains need coverage.
After DNS changes propagate, use Microsoft Remote Connectivity Analyzer's Exchange Autodiscover test for an account in each domain. Investigate any DNS, certificate, or endpoint errors reported.

Use WPS Office for Documents During Your Exchange Migration
WPS Office is a free, lightweight alternative for everyday document work. Its familiar interface and Microsoft Office format compatibility make it easier to move existing files while you manage your Exchange migration separately.

Frequently Asked Questions
Can I use SRV-based Autodiscover redirection in this Exchange hybrid deployment?
Do not rely on SRV-based Autodiscover redirection for this hybrid scenario. Configure standard HTTPS Autodiscover with an appropriate DNS record and certificate coverage for each required domain.
What should each Autodiscover CNAME point to?
Point each autodiscover.<domain> CNAME to the Autodiscover endpoint appropriate for your hybrid topology. Verify the target against your deployment configuration and current Microsoft guidance before changing DNS.
Will one wildcard certificate cover unrelated email domains?
No. A wildcard such as *.a.com does not cover autodiscover.b.com. A SAN or UCC certificate can cover names across multiple domains; confirm the available options with your certificate provider.
How can I check whether Autodiscover works after changing DNS?
Run the Exchange Autodiscover test in Microsoft Remote Connectivity Analyzer for an account in each domain after DNS changes propagate. Review the results for DNS, certificate, and endpoint errors.




