Lenblock
asked on
Office 365 Hybrid Autodiscover DNS
Hi
Recently we got Office 365, Exchange online hybrid solution.
We will both have on premise users with Exchange and office 365 users.
We have split brain DNS.
Struggling a bit with autodiscover.
How can we both have autodiscover for Exchange and autodiscover for Office 365 ?
Tried creating a cname to test:
autodisover.contoso.com -> outlook.autodiscover.com
*Cannot be created because it collides with AA Record autodiscover.contoso.com
Regards.
Recently we got Office 365, Exchange online hybrid solution.
We will both have on premise users with Exchange and office 365 users.
We have split brain DNS.
Struggling a bit with autodiscover.
How can we both have autodiscover for Exchange and autodiscover for Office 365 ?
Tried creating a cname to test:
autodisover.contoso.com -> outlook.autodiscover.com
*Cannot be created because it collides with AA Record autodiscover.contoso.com
Regards.
Last Comment
ASKER
Hi
Tried that and we get a timeout when trying to configure Outlook.
Any idea where to start looking ?
Regards.
Tried that and we get a timeout when trying to configure Outlook.
Any idea where to start looking ?
Regards.
When you say a timeout, is it working for the on premise users but not the cloud users? Or is it not working for anyone?
Can you try the Autodiscover test at www.exrca.com. Try the test for an on premise mailbox and a cloud mailbox and post the results here.
Can you try the Autodiscover test at www.exrca.com. Try the test for an on premise mailbox and a cloud mailbox and post the results here.
ASKER
Testing internally now with Outlook, also did a test exrca and it failed.
Two of our services on the ADFS-Proxy is failing to start.
Active Directory Federation Services
The federation server proxy could not be started.
Reason: Error retrieving proxy configuration from the Federation Service.
Additional Data
Exception details:
An error occurred when attempting to load the proxy configuration.
Web Application Proxy Service
The Web request failed because the web.config file is malformed.
User Action:
Fix the malformed data in the web.config file.
Exception details:
Root element is missing. (C:\Windows\ADFS\Config\mi
Root element is missing.
Checked the file "microsoft.identityServer.
Two of our services on the ADFS-Proxy is failing to start.
Active Directory Federation Services
The federation server proxy could not be started.
Reason: Error retrieving proxy configuration from the Federation Service.
Additional Data
Exception details:
An error occurred when attempting to load the proxy configuration.
Web Application Proxy Service
The Web request failed because the web.config file is malformed.
User Action:
Fix the malformed data in the web.config file.
Exception details:
Root element is missing. (C:\Windows\ADFS\Config\mi
Root element is missing.
Checked the file "microsoft.identityServer.
ASKER
Result from EXRCA (translated from norwegian)
Received a HTTP 401 Unauthorized response from remote ISA Server . This is usually due to an incorrect username or password. If you try to log on to an Office 365 service , ensure that you use your full user principal ( UPN ) .
HTTP response headers :
Connection: Keep- Alive
Pragma : no-cache
Content-Length : 2073
Cache -Control : no-cache
Content-Type : text / html
WWW Authenticate : Basic realm = " "
Elapsed time : 1014 ms .
Checks for a CNAME record for Autodiscover in DNS for the domain contoso.com Office 365 .
Unable to validate CNAME record for Autodiscover in DNS. If the mailbox is not in Office 365 , you can ignore this warning.
There is no Autodiscover CNAME record for your domain contoso.com .
Elapsed time : 182 ms .
Received a HTTP 401 Unauthorized response from remote ISA Server . This is usually due to an incorrect username or password. If you try to log on to an Office 365 service , ensure that you use your full user principal ( UPN ) .
HTTP response headers :
Connection: Keep- Alive
Pragma : no-cache
Content-Length : 2073
Cache -Control : no-cache
Content-Type : text / html
WWW Authenticate : Basic realm = " "
Elapsed time : 1014 ms .
Checks for a CNAME record for Autodiscover in DNS for the domain contoso.com Office 365 .
Unable to validate CNAME record for Autodiscover in DNS. If the mailbox is not in Office 365 , you can ignore this warning.
There is no Autodiscover CNAME record for your domain contoso.com .
Elapsed time : 182 ms .
Definitely look at the AD FS issue first, manually editing those files can easily mess up the XML formatting. EO will always hit the AD FS proxy server, so that explains your autodiscover troubles.
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Reinstalling the role on the ADFS-Proxy solved the issue.
Exchange
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.
213K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
In a hybrid situation you would just point your autodiscover record to your on premise Exchange servers. Through the hybrid configuration your on premise servers know what mailboxes are local and what are in the cloud.