AD DNS Crashed and recreated but DC not working

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)
jobby1Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mike KlineCommented:
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
David Johnson, CD, MVPOwnerCommented:
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
jobby1Author Commented:
I tired to restart the netlogon  and restarted  the whole server also no use. Still same error.
0
jobby1Author Commented:
I restored the old backup. Some machines I rejoined to domain again. Now ok
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jobby1Author Commented:
I tried many options finally I restored the backup it is ok now.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.