Month: May 2018

Microsoft Exchange Server 2016 – Autodiscover DNS Lookup

The autodiscover service is critical to the proper functioning of a Microsoft Exchange Server 2016 infrastructure. Additionally, the autodiscover service may be utilized using SCP for domain joined clients or DNS records for external clients. The DNS records and associated URLs will be utilized, in the order below, to find the autodiscover XML file. More information regarding autodiscover may be found here.

A or CNAME (

A or CNAME (

A or CNAME (


Domain Name System – Propagation

I recently decided to test a Domain Name System (DNS) provider expansion with GoDaddy and  ClouDNS (link here) for a proof of concept using the domain name The initial configuration and testing were successful. However, after I made the decision to host all DNS service with GoDaddy (again, it was a proof of concept) I found a large quantify of name server around the globe contained name server (NS) records for with entries pointing to ClouDNS name servers (,,, and using Whats My DNS? (link here). I found this odd due to the fact that the GoDaddy DNS management interface only contained (2) NS records ( and which are the authoritative for the domain and the ClouDNS name servers are no longer hosting zone files or responding to DNS queries for Additionally, the Time to Live (TTL) was a maximum of (1) hours. So, I didn’t expect to find inconsistencies days later.

So, what could be causing the lack of synchronization in the NS records (remember, DNS is a distributed and hierarchial system by nature)? Upon basic troubleshooting I found that the GoDaddy name servers and did not contain the same NS records for using the nslookup utility (please see the screen shots below). I have contacted GoDaddy support and they have provided me with assurance that they will manually delete the NS records of,,, and from