<div>
Yes all looks good. <br />
<br />
SRV record looks perfect!
</div>


<div>
Does it seem correct considering my public DNS record / cert is mail.mydomain.com? &nbsp;Recently I've been deploying exchange server with autodiscover for the public DNS record and cert. &nbsp;But this environment already existed with mail.mydomain.com for the public DNS and cert.
</div>


<div>
From what I understand from your explanation is that your cName record is looping to your A record so you can auto discover via your CNAME &gt;&nbsp;srv record? <br />
<br />
If that's what you aiming for, logically to me it makes sense!
</div>


<div>
Correct. &nbsp;That is what I was trying to accomplish. &nbsp; I'm also running split DNS. But.. &nbsp;On all internally referenced DNS records I have matching records. &nbsp; It seems the ISP messed up their part of it. &nbsp;They are looking at it again tomorrow. <br />
<br />
I'll update this post then.
</div>


<div>
Great, let me know how it works out!
</div>


<div>
I'm still having issues.. &nbsp;So.. &nbsp;The Microsoft Remote Connectivity Analyzer results in the below output error.. &nbsp;Aside from that the test is okay.. &nbsp;Now. &nbsp;My cert is for mail.mydomain.com and not autodiscover.mydomain.com . &nbsp;And.. &nbsp;The external server / DNS is mail.mydomain.com . &nbsp;This is also how Exchange 2010 shows my external host to be.. &nbsp;and the internal. &nbsp;What am I doing wrong? &nbsp;I need it to want to assume mail.mydomain.com is the external DNS and cert to expect.<br />
<br />
Host name autodiscover.mydomain.com doesn't match any name found on the server certificate CN=Not Secure, OU=Not Secure, O=Not Secure, L=Not Secure, S=Not Secure, C=NS.<br />
Elapsed Time: 0 ms.
</div>


<div>
Also.. The redirection method fails with the below. &nbsp;The thing is.. If I go to (in a browser) autodiscover.mydomain.com it redirects https://mail.mydomain.com/Autodiscover/Autodiscover.xml&nbsp;just fine.. &nbsp;<br />
<br />
The Microsoft Connectivity Analyzer is checking the host autodiscover.drexchem.com for an HTTP redirect to the Autodiscover service.<br />
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover.<br />
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Additional Details<br />
&nbsp; &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<br />
A Web exception occurred because an HTTP 404 - NotFound response was received from IIS7.<br />
HTTP Response Headers:<br />
Content-Length: 1245<br />
Content-Type: text/html<br />
Date: Tue, 05 Jan 2016 17:49:16 GMT<br />
Server: Microsoft-IIS/7.5<br />
X-Powered-By: ASP.NET<br />
Elapsed Time: 124 ms.
</div>


<div>
Gopher, I'm a little lost now and don't have any ideas for you. Hopefully another expert is able to assist on the situation.
</div>


<div>
I'm going to try to point the SRV record to mail.mydomain.com versus autodiscover.mydomain.com . &nbsp;Based on the errors I'm getting when using the Microsoft Remote Connectivity tester it seems it's trying to access autodiscover.mydomain.com directly for it's reporting a SSL cert mismatch. &nbsp;I need to access mail.mydomain.com .
</div>


<div>
I need to make the SRV record as below since my external/internal DNS is mail.mydomain.com and not autodiscover.mydomain.com . &nbsp;Not sure how to get the other methods to work. &nbsp;The SRV method is all I need.<br />
<br />
Create a SRV record of the below values:<br />
_autodiscover<br />
_tcp<br />
@<br />
0<br />
0<br />
443<br />
mail.mydomain.com
</div>


<div>
<div class="content wysiwyg-content">
The public DNS record and cert for my Exchange server is mail.mydomain.com. &nbsp;I have a single server holding all roles. &nbsp;It's internal and external DNS record is the same internally and externally. &nbsp;This being mail.mydomain.com. &nbsp;I'm trying to get autodiscover setup. &nbsp;Below is what I requested for my ISP. &nbsp;They manage my public DNS records for me.. &nbsp;I manage the Exchange server onsite and the IIS server onsite used for the redirect. &nbsp;Is this correct? &nbsp;Also.. &nbsp;The redirect.mydomain.com website has HTTP redirect redirecting to https://mail.mydomain.com/Autodiscover/Autodiscover.xml&nbsp;. &nbsp;With that said.. &nbsp;Is my request below correct?<br />
<br />
Create an A record of redirect.mydomain.com and point it to publicIPaddress<br />
&nbsp;<br />
Create a CNAME record of 'autodiscover' for our domain of mydomain.com with a value of redirect.mydomain.com<br />
&nbsp;<br />
Create a SRV record of the below values:<br />
_autodiscover<br />
_tcp<br />
@<br />
0<br />
0<br />
443<br />
autodiscover.mydomain.com
</div>
</div>


The public DNS record and cert for my Exchange server is mail.mydomain.com.  I have a single server holding all roles.  It's internal and external DNS record is the same internally and externally.  This being mail.mydomain.com.  I'm trying to get autodiscover setup.  Below is what I requested for my ISP.  They manage my public DNS records for me..  I manage the Exchange server onsite and the IIS server onsite used for the redirect.  Is this correct?  Also..  The redirect.mydomain.com website has HTTP redirect redirecting to https://mail.mydomain.com/Autodiscover/Autodiscover.xml .  With that said..  Is my request below correct?

Create an A record of redirect.mydomain.com and point it to publicIPaddress
 
Create a CNAME record of 'autodiscover' for our domain of mydomain.com with a value of redirect.mydomain.com
 
Create a SRV record of the below values:
_autodiscover
_tcp
@
0
0
443
autodiscover.mydomain.com

autodiscover for Exchange 2010 when autodiscover DNS is different than external DNS for mail server

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.