Cannot Join Windows Domain from a Windows 10 Pro Workstation
I have a Windows 10 Pro (64-bit) workstation that I need to join to a domain.
The domain name is ALLSEASONS.local.
When I go to join the computer, I get the following error. Can someone help me figure out what I am doing wrong?
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 "ALLSEASONS.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.ALLSEASONS.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:
10.1.1.67
- One or more of the following zones do not include delegation to its child zone:
ALLSEASONS.local
local
. (the root zone)
The domain name is ALLSEASONS.local.
When I go to join the computer, I get the following error. Can someone help me figure out what I am doing wrong?
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 "ALLSEASONS.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.ALLSEASONS.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:
10.1.1.67
- One or more of the following zones do not include delegation to its child zone:
ALLSEASONS.local
local
. (the root zone)
Last Comment
The error was: "DNS name does not exist."
check your dns settings
is the domain name resolvable?
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Scott Silva: DHCP
And I assume it is on the proper network to reach the domain controller?
Not possibly in a different subnet that doesn't have access to the DC like a guest network?
Network is actually working... Can load a basic web page...
Not possibly in a different subnet that doesn't have access to the DC like a guest network?
Network is actually working... Can load a basic web page...
SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Scott Silva: Correct
ASKER
I want to thank everyone for their suggestions. It turned out to be something really stupid on my part.
I say stupid because I know better but for whatever reason, I had forgotten. The advice that I got did lead me to the solution. So THANK YOU ALL!
When I ran the NSLOOKUP, the information that was returned showed me IPV6 addresses. :(
I always turn that off in the NIC but evidently lost my head and forgot on this PC.
Seeing those addresses, I turned off IPV6 and eureka....everything worked fine.
Have a great weekend all! :)
I say stupid because I know better but for whatever reason, I had forgotten. The advice that I got did lead me to the solution. So THANK YOU ALL!
When I ran the NSLOOKUP, the information that was returned showed me IPV6 addresses. :(
I always turn that off in the NIC but evidently lost my head and forgot on this PC.
Seeing those addresses, I turned off IPV6 and eureka....everything worked fine.
Have a great weekend all! :)
ASKER
How do I close this ticket? I haven't used EE in a long time.
Select the questions which are the solution or those that helped. you can choose multiple comments that helped identify and resolve your issue.
Windows OS
This topic area includes legacy versions of Windows prior to Windows 2000: Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions including Windows Mobile.
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
If using a fixed address, make sure there are no typos in the dns settings.