Hybrid Exchange - Autodiscover records for on-premise

%3CLINGO-SUB%20id%3D%22lingo-sub-569807%22%20slang%3D%22en-US%22%3EHybrid%20Exchange%20-%20Autodiscover%20records%20for%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-569807%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20everyone%20is%20well.%20I%20needed%20some%20advice%20please.%20My%20internal%20domain%20is%20mycompany.local%20and%20the%20external%20domain%20name%20is%20mycompany.co.za.%20On%20the%20on-premise%20DNS%20servers%20I%20noticed%20we%20had%20static%20A%20records%20configured%20namely%3A%20autodiscover.mycompany.local%20and%20autodiscover.mycompany.co.za%20both%20of%20which%20resolved%20to%20the%20internal%20IP%20of%20the%20exchange%20server.%20The%20public%20DNS%20A%20record%20for%20autodiscover.mycompany.co.za%20pointed%20to%20my%20TMG.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20in%20attempt%20to%20point%20my%20autodiscover%20records%20to%20Office%20365%20I%20deleted%20those%202%20static%20A%20records%20from%20the%20on-prem%20DNS%20server.%20I%20then%20changed%20the%20public%20facing%20DNS%20record%20for%20autodiscover%20and%20pointed%20it%20to%20Office%20365.%20The%20problem%20now%20is%20that%20within%20the%20LAN%20autodiscover.mycompany.co.za%20is%20not%20resolving.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20advice%20on%20best%20how%20I%20can%20resolve%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-569807%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Server%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570229%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Exchange%20-%20Autodiscover%20records%20for%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570229%22%20slang%3D%22en-US%22%3E%3CP%3EWhile%20in%20Hybrid%2C%20keep%20the%20autodiscover%20record%20pointing%20to%20on-premises.%20And%20keep%20the%20internal%20record%20as%20well.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-570530%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Exchange%20-%20Autodiscover%20records%20for%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570530%22%20slang%3D%22en-US%22%3EBut%20specifically%20in%20your%20case%20you%20deleted%20AutoDiscover%20from%20your%20internal%20DNS%20zone%20of%20mycompany.co.za%20so%20you%20cannot%20resolve%20that%20record%20inside%20the%20company.%20You%20need%20either%20to%20have%20a%20cname%20for%20AutoDiscover%20inside%20that%20DNS%20zone%20or%20do%20as%20%40vasil%20says%20and%20point%20AutoDiscover%20at%20your%20onprem%20Exchange%20management%20server%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-572790%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Exchange%20-%20Autodiscover%20records%20for%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-572790%22%20slang%3D%22en-US%22%3EHi%20Vasil.%20Thank%20you%20for%20that%20suggestion%20but%20I%20want%20to%20limit%20the%20dependency%20on%20the%20on-premise%20exchange.%20All%20of%20my%20mailboxes%20have%20been%20moved%20into%20Office%20365.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-572996%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Exchange%20-%20Autodiscover%20records%20for%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-572996%22%20slang%3D%22en-US%22%3EThanks%20Brian.%20So%20create%20a%20CNAME%20in%20my%20internal%20DNS%20zone%20pointing%20to%20autodiscover.outlook.com%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-574570%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Exchange%20-%20Autodiscover%20records%20for%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-574570%22%20slang%3D%22en-US%22%3EA%20CNAME%20for%20AutoDiscover%20pointing%20to%20the%20name%20-%20yes.%20Just%20a%20CNAME%2C%20no%20that%20would%20not%20be%20correct%3CBR%20%2F%3E%3CBR%20%2F%3Eautodiscover%20CNAME%20outlook.office.com%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-615537%22%20slang%3D%22en-US%22%3ERe%3A%20Hybrid%20Exchange%20-%20Autodiscover%20records%20for%20on-premise%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-615537%22%20slang%3D%22en-US%22%3EHi%20Brian%3CBR%20%2F%3E%3CBR%20%2F%3EDon't%20quite%20understand%20you%20here%3A%3CBR%20%2F%3E%22A%20CNAME%20for%20AutoDiscover%20pointing%20to%20the%20name%20-%20yes.%20Just%20a%20CNAME%2C%20no%20that%20would%20not%20be%20correct%22%3C%2FLINGO-BODY%3E
Highlighted
Regular Contributor

Hi All

 

Hope everyone is well. I needed some advice please. My internal domain is mycompany.local and the external domain name is mycompany.co.za. On the on-premise DNS servers I noticed we had static A records configured namely: autodiscover.mycompany.local and autodiscover.mycompany.co.za both of which resolved to the internal IP of the exchange server. The public DNS A record for autodiscover.mycompany.co.za pointed to my TMG. 

 

So in attempt to point my autodiscover records to Office 365 I deleted those 2 static A records from the on-prem DNS server. I then changed the public facing DNS record for autodiscover and pointed it to Office 365. The problem now is that within the LAN autodiscover.mycompany.co.za is not resolving.

 

Any advice on best how I can resolve this?

6 Replies
Highlighted

While in Hybrid, keep the autodiscover record pointing to on-premises. And keep the internal record as well.

Highlighted
But specifically in your case you deleted AutoDiscover from your internal DNS zone of mycompany.co.za so you cannot resolve that record inside the company. You need either to have a cname for AutoDiscover inside that DNS zone or do as @vasil says and point AutoDiscover at your onprem Exchange management server
Highlighted
Hi Vasil. Thank you for that suggestion but I want to limit the dependency on the on-premise exchange. All of my mailboxes have been moved into Office 365.
Highlighted
Thanks Brian. So create a CNAME in my internal DNS zone pointing to autodiscover.outlook.com?
Highlighted
A CNAME for AutoDiscover pointing to the name - yes. Just a CNAME, no that would not be correct

autodiscover CNAME outlook.office.com
Highlighted
Hi Brian

Don't quite understand you here:
"A CNAME for AutoDiscover pointing to the name - yes. Just a CNAME, no that would not be correct"