Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a server which is running dns,terminal,ad,etc and I am trying to get desktop computer to join the domain.

My server names is (dont ask me why its so long) The domain is

My server ip is and when trying to get a pc on the domain I get the following message:

: 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 a domain controller for domain

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

The query was for the SRV record for

Common causes of this error include the following:

  • The DNS SRV record is not registered in DNS.

  • One or more of the following zones do not include delegation to its child zone: com . (the root zone)

For information about correcting this problem, click Help.

what should I do?

share|improve this question
up vote 2 down vote accepted

If I had to take a guess based on the information provided, I'd guess that the PC isn't using the domain controller for DNS. If you only have one DC, make sure the the only thing in your client computers' DNS server list is

And it should go without saying that if you do only have one domain controller, you should work on getting a second ASAP, make it run DNS as well, and add it as a secondary DNS server to your clients.

share|improve this answer
why a second? Oh so your saying the computer im trying to make join the domain is poin to maybe my firewall or ISP DNS? – user160605 Feb 19 '13 at 16:33
You should always have at least two Domain Controllers for any domain. You might want to read through the AD Basics Q&A that I wrote here. It covers a lot of stuff about AD that might be worth reading. – MDMarra Feb 19 '13 at 16:37
And to answer your second question, you should really only point your clients that are AD joined to use DNS services provided by your domain controllers unless you really know what you're doing. Just do an ipconfig /all and see if your domain controller is listed as the DNS server for the client. If it isn't, you need to change your configuration. – MDMarra Feb 19 '13 at 16:38
worked thanks so much.. – user160605 Feb 19 '13 at 17:14
Works! Thanks a lot! – Envil Aug 3 '15 at 4:59

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.