Troubleshooting failure to install of Exchange 2010 due to DNS issues

by Mitch Tulloch [Published on 8 Feb. 2011 / Last Updated on 8 Dec. 2009]

What to do if you try to install Exchange 2010 and get an error saying that the DNS server could not be resolved.

Here's a troubleshooting tip from a colleague of mine who is a Microsoft field consultant and was trying to install Exchange 2010. The problem was that the Exchange install was failing because it could not resolve the DNS server, which was also the domain controller.

After hours of frustration trying to reboot the server and tweak various settings, he read over the troubleshooting section of the Windows Server 2008 Active Directory Resource Kit and discovered that he could re-populate the records in DNS by stopping and then restarting the Netlogon service on the domain controller. Once he did this, his Exchange install proceeded smoothly. Shows what a good book can do when you need it!

If you have feedback concerning this tip, please email me. And be sure to check out my website!

The Author — Mitch Tulloch

Mitch Tulloch is a widely recognized expert on Windows administration, networking, and security. He has been repeatedly awarded Most Valuable Professional (MVP) status by Microsoft for his outstanding contributions in supporting users who deploy and use Microsoft platforms, products and solutions. Mitch has published over two hundred articles on different IT websites and magazines, and he has written or contributed to almost two dozen books and is lead author for the Windows 7 Resource Kit from Microsoft Press. For more information, see .

Latest Contributions

Featured Links