<div>
Remove the wildcard DNS record.
</div>


<div>
ok. I assume this will take 24hrs to see if that corrects the issue
</div>


<div>
Try deleting an Outlook profile and re-creating it. &nbsp;I've had that fix cert issues as you describe.
</div>


<div>
ScottCha- the bigger issue is that the Microsoft Exchange Connectivity Test is reporting incorrect data.
</div>


<div>
That's because it cycles through to an A record query (autodiscover.domain.com) and the wildcard WAN IP is returned. &nbsp;You should be able to just click OK in the Outlook warning and it will eventually find the correct settings. &nbsp;Not really a sustainable option long term, but Outlook should still technically work.
</div>


<div>
Well it has been 48hrs and the exchange test is still failing and showing the same info attached in the original post. The wildcard A record is gone and has been gone for 48hrs??? What's up with this?
</div>


<div>
Jason- just sent you the message with full detail
</div>


<div>
<div class="content wysiwyg-content">
we added a certificate to our on premise exchange server and ran an exchange connectivity test. The certificate isn't showing correctly. furthermore, the autodiscover isn't showing correctly either? Yet, I can go to owa.xxxxxxxx.com/mail and it pulls up the correct login page, authenticates, doesn't have certificate warnings? Outlook users are getting cert warnings. <br />
<br />
I checked the hosting company and the mx is correct, autodiscover record is correct ip as well. the website is hosted elsewhere so it has a different public ip address and that is what the exchange server test is pulling.<br />
<br />
See attached. for a portion of the exchange test and the other attachment is the DNS records with hosting company. Autodiscover is 96.x.x.218, but the exchange test shows 108.x.x.217?<br />
<br />
Cert shown in the exchange test is also entirely incorrect as we use one from Godaddy.<br />
<a href="https://filedb.experts-exchange.com/incoming/2016/02_w07/1081177/dns.jpg" target="_blank" class="file-inline" title="Hosting company DNS (21 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>dns.jpg</a><br />
<a href="https://filedb.experts-exchange.com/incoming/2016/02_w07/1081178/test.jpg" target="_blank" class="file-inline" title="Exchange Connectivity Test snapshot (137 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>test.jpg</a>
</div>
</div>


dns.jpg

test.jpg

we added a certificate to our on premise exchange server and ran an exchange connectivity test. The certificate isn't showing correctly. furthermore, the autodiscover isn't showing correctly either? Yet, I can go to owa.xxxxxxxx.com/mail and it pulls up the correct login page, authenticates, doesn't have certificate warnings? Outlook users are getting cert warnings. 

I checked the hosting company and the mx is correct, autodiscover record is correct ip as well. the website is hosted elsewhere so it has a different public ip address and that is what the exchange server test is pulling.

See attached. for a portion of the exchange test and the other attachment is the DNS records with hosting company. Autodiscover is 96.x.x.218, but the exchange test shows 108.x.x.217?

Cert shown in the exchange test is also entirely incorrect as we use one from Godaddy.

Exchange Connectivity Test not showing correctly

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.

Exchange

Microsoft Outlook is a personal information manager from Microsoft, available as a part of the Microsoft Office suite. Although often used mainly as an email application, it also includes a calendar, task manager, contact manager, note-taker, journal, and web browser.

Outlook

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.