Link to home
Start Free TrialLog in
Avatar of snoopaloop
snoopaloopFlag for United States of America

asked on

THe Active Directory DOmain Controller (AD DC) for the domain "che.local" could not be contacted

This one machine that I like to join will not join.  Just joined another machine with no issues.  I can ping the Domain controller with no issues and the DNS on the machine with the issue is pointed to the DC as well.  Below is the error message...



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 "che.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.che.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:

192.168.1.250

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

che.local
Avatar of Tom Cieslik
Tom Cieslik
Flag of United States of America image

If your DC is che.local and this  server IP is 192.168.1.250
then just open Notepad as Administrator
go to  c:\windows\system32\drivers\etc

Open host file (you need to change notepad filtering for extension to All since host has no extension)

Create record

192.168.1.250       che.local

Save and close

Now your computer should have no problem to join to domain che.local
SOLUTION
Avatar of MacGyver80
MacGyver80
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of snoopaloop

ASKER

Same error message after flushdns, etc.  @Tom,  I'm a little against your request because it could come back to haunt me if we change the network IP.
Just one.  I've added two other to the domain.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
No issues considering three other workstations just connected with no problems.  

Regarding Tom's suggestion.   Just an issue if we ever change the DC IP.  Seems like not the ideal solution but I'm over it so I gave it go.  Unfortunately, it did not work.   I may refresh Windows 10.
I mounted the 10 ISO and ran windows 10 setup.   Same error.  It may need a complete wipe or some serious troubleshooting.
Why you want to change network IP for Domain Controller ???
After you join computer to domain you can remove this entries from Host file
The network was setup with not a very scalable IP range segment.  Anyway, the host file didnt work.
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
yeah, it's crashing too.  We are sending the computer back.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial