To workaround this issue, until a more permanent solution can be applied, you may use the following Registry settings to force Outlook to bypass the root domain discovery and redirect to the autodiscover CNAME or A record to resolve the address for autodiscover settings. Most organizations use a autodiscover CNAME or A record to resolve the autodiscover address, which is also the recommended solution for both on on-premise Exchange deployment and when all mailboxes are placed in Exchange Online.

The situation is furthermore complicated when the option to manually enter the Exchange server settings is removed in Outlook 2016.Ĭommon for these cases is that the internal autodiscover CNAME record is added in a split-DNS zone and resolves to – straight out of the Office 365 domain registration wizard.ĭigging deeper, the Test E-mail AutoConfiguration reveals that the autodiscover process is delayed by a series of (16) queries and the subsequent timeout for autodiscover settings from the root domain, like. As the use of Office 2016 has started to gain momentum, a number of organizations have experienced cases where Outlook 2016 take extraordinary long time to setup a new profile with a hosted Exchange 2010/2013 solution, like Exchange Online.

Outlook autodiscover on mac hack