Joining a newly created 2008 domain now need help

**Der Rabe** · 11-01-2009, 12:03 PM

I am running windows standard server 2008 sp. I just installed it and set it up to be a domain controller using a guide I found online. I set up my user accounts in AD. Now I want to join my home computers to the new domain. I get the following error.

Code:

An active directory domain controller (AD DC) for the domain "xxxx.com" could not be contacted.

Ensure that the domain name is typed correctly.

If the name is correct, click Details for Troubleshooting information.

[details]
Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\Windows\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "xxxx.com":

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.xxxx.com

Common causes of this error include the following:

- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

192.168.0.1

- One or more of the following zones do not include delegation to its child zone:

xxxx.com
com
. (the root zone)

I am fairly new to setting up a domain controller, from what I am reading it is looking for the dc on the wrong ip address. The servers ip is 192.168.0.100. I do not know how to setup the DNS. and I am looking for help.

Also 192.168.0.1 is the IP address of my router which I want to be my dhcp server and firewalls etc. I just want the server for the network authentication and to run a web page. My router is a d-link router if that helps

skeptikal · 11-01-2009, 02:31 PM

You are likely getting this error due to an erroneous dns server setup. Download and install the windows server support tools from Microsoft and run the command prompt.exe from within the support tools folder in program files. this will start the cmd prompt in the proper directory. Type DCDiag /Test:DNS. This should tell you where the problem lies in your dns server.

//edit: Looks like the support tools for server 2008 are actually included on the install discs. Found this quote on another site:

"You may ask where is the Windows Server 2008 support tools? On Server 2008 support tools are located in "support\tools" directory on the Windows Server 2008 CD, extract support.cab to the directory on your server. UPDATE: I just talk to someone from Microsoft. Most of Support Tools for Server 2008 should be included in "Remote Server Administration Tools". Go to Add Features > Install Remote Server Administration Tools."

Hope this helps! With all of that said once you have your DNS server set up correctly everything should work out. I had to remove all the roles on my server and re-add them with all the correct dns addresses before it worked. Hopefully you will not have to do this.

**Der Rabe** · 11-01-2009, 03:18 PM

Thank you for your response. I did figure out my issue sort of, I just had to point the dns server on each computer manually instead of using obtain automatically. Since I only have a few computers to setup it was an acceptable solution. But how would I set it up to automatically detect for future computers.

skeptikal · 11-01-2009, 03:47 PM

So did you use your server ip as the dns address on the dhcp client machines?

You might check that your dns server has the forwarders set to your isp's dns server addresses. To be honest though without sitting in front of one of my servers at work I don't know how to tell you to do that. I think that would allow your server to handle all of the dns tasks and your clients to stay set to obtain auto...

**Der Rabe** · 11-01-2009, 07:25 PM

I made the primary dns the server and my router as the secondary and seems to be working flawlessly

11-01-2009, 02:31 PM	#2 (permalink)
skeptikal Registered User Join Date: Oct 2009 Posts: 11 OS: XP Pro SP3	Re: Joining a newly created 2008 domain now need help You are likely getting this error due to an erroneous dns server setup. Download and install the windows server support tools from Microsoft and run the command prompt.exe from within the support tools folder in program files. this will start the cmd prompt in the proper directory. Type DCDiag /Test:DNS. This should tell you where the problem lies in your dns server. //edit: Looks like the support tools for server 2008 are actually included on the install discs. Found this quote on another site: "You may ask where is the Windows Server 2008 support tools? On Server 2008 support tools are located in "support\tools" directory on the Windows Server 2008 CD, extract support.cab to the directory on your server. UPDATE: I just talk to someone from Microsoft. Most of Support Tools for Server 2008 should be included in "Remote Server Administration Tools". Go to Add Features > Install Remote Server Administration Tools." Hope this helps! With all of that said once you have your DNS server set up correctly everything should work out. I had to remove all the roles on my server and re-add them with all the correct dns addresses before it worked. Hopefully you will not have to do this. Last edited by skeptikal; 11-01-2009 at 02:37 PM.

11-01-2009, 03:18 PM	#3 (permalink)
Der Rabe Watching from the shadows Join Date: Jun 2002 Location: Currently In Michigan Posts: 1,140 OS: XP Sp3, Vista sp1, 2003 sp2	Re: Joining a newly created 2008 domain now need help Thank you for your response. I did figure out my issue sort of, I just had to point the dns server on each computer manually instead of using obtain automatically. Since I only have a few computers to setup it was an acceptable solution. But how would I set it up to automatically detect for future computers.

11-01-2009, 03:47 PM	#4 (permalink)
skeptikal Registered User Join Date: Oct 2009 Posts: 11 OS: XP Pro SP3	Re: Joining a newly created 2008 domain now need help So did you use your server ip as the dns address on the dhcp client machines? You might check that your dns server has the forwarders set to your isp's dns server addresses. To be honest though without sitting in front of one of my servers at work I don't know how to tell you to do that. I think that would allow your server to handle all of the dns tasks and your clients to stay set to obtain auto...

11-01-2009, 07:25 PM	#5 (permalink)
Der Rabe Watching from the shadows Join Date: Jun 2002 Location: Currently In Michigan Posts: 1,140 OS: XP Sp3, Vista sp1, 2003 sp2	Re: Joining a newly created 2008 domain now need help I made the primary dns the server and my router as the secondary and seems to be working flawlessly