Solved

AD DNS Crashed and recreated but DC not working

Posted on 2014-02-26
5
218 Views
Last Modified: 2014-05-31
My DNS and AD running in the same machine windows 2008 R2. But my DNS corrupted so I removed and add the DNS again but I am getting the below error when I join any PC to the domain.


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 "xxx.local":

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.xxx.local

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:


12.47.92.60
12.77.92.45
172.68.1.2

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

xxx.local
local
. (the root zone)
0
Comment
Question by:jobby1
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
5 Comments
 
LVL 57

Expert Comment

by:Mike Kline
ID: 39888492
Restart the netlogon service on that DC to see if it registers the SRV records again.    When you say AD crashed can you tell us a bit more about that.  

What errors are you seeing in your logs?

Thanks

Mike
0
 
LVL 81

Expert Comment

by:David Johnson, CD, MVP
ID: 39889107
12.47.92.60
12.77.92.45
172.68.1.2


172.68.1.2 should be the first entry
12747.92.60 AND 12.77.92.45 ATT DNS servers should NOT be here
either use forwarders or use root hints
0
 

Author Comment

by:jobby1
ID: 39891070
I tired to restart the netlogon  and restarted  the whole server also no use. Still same error.
0
 

Accepted Solution

by:
jobby1 earned 0 total points
ID: 40091001
I restored the old backup. Some machines I rejoined to domain again. Now ok
0
 

Author Closing Comment

by:jobby1
ID: 40102430
I tried many options finally I restored the backup it is ok now.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
Auditing domain password hashes is a commonly overlooked but critical requirement to ensuring secure passwords practices are followed. Methods exist to extract hashes directly for a live domain however this article describes a process to extract u…
This tutorial will walk an individual through the steps necessary to enable the VMware\Hyper-V licensed feature of Backup Exec 2012. In addition, how to add a VMware server and configure a backup job. The first step is to acquire the necessary licen…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question