Sunday, March 27, 2011

Adding a Windows Server 2008 to a Small Business Active Directory Domain with Router DHCP Enabled


You are trying to add a new Windows Server 2008 machine to a relatively new domain created on a network that was originally peer-to-peer and still has a gateway acting as both router and DHCP server, and you experience the following error whenever you attempt to join this server to the new domain:
An attempt to resolve the dns name of a domain controller in the domain being joined has failed...
In this case, your Windows 2008 server is confused.  When it came online, it received its IP configuration information from one DHCP server (a race condition is involved here).  Then, when it attempts to join the domain, it contacts that old DNS address, but finds that it doesn't get the appropriate information.  The best solution is to simply stop DHCP on the gateway, but there may be complex issues for small businesses that require a transition period in which both DHCP servers remain enabled. In any case, the solution is trivial and is discussed here.


On the Windows Server 2008 machine, go: Local Area Connection > Properties > Internet Protocol Version 4 > Properties.  On the General tab, select the option Use the following DNS server addresses.  For DNS address, enter the IP address of your new domain controller.  Then try to rejoin the domain.

  1. Failed to resolve DNS name in domain contrler
  2. an attempt to resolve the dns name of a dc in the domain being joined has failed.Please verify this client is configured to reach a DNS server that can resolve DNS name in the target domain
  3. An Attempt To Resolve The Dns Name Of A Domain Controller In The Domain Being Joined Has Failed
  4. Dns error windows 7 connect to domain
  • You may find that you didn't have to change the DNS setting at all, but that simply trying to rejoin the domain at a later time is successful.

No comments: