Thursday, 13 August 2015

Unable to add client PC (VM) to Domain controller (VM) running on Hyper-V host

I would like to share my knowledge I gained while troubleshooting IT related issues. Recently, I set up a Host server that runs Windows Server 2012 Standard R2. I made this server as my Hyper-V host. My plan was to add few VMs and setup my own small lab at home.
I added a VM on my host PC that runs Windows Server 2012 Standard R2. I made this VM as my domain controller ( I setup few users and group policies. Then I added another VM that runs Windows 10. I wanted to add this PC to domain so that I can test group policies and other stuff. But, while trying to add my client PC to domain, I received an error message.
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 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 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:
- One or more of the following zones do not include delegation to its child zone:
. (the root zone)
For information about correcting this problem, click Help.
I was a bit surprised as I could ping all three PCs (host PC, DC1 and Win 10 PC) from each other and from a laptop. I could even RDP to all 3 PCs. I have rechecked all IP configurations on DC1 and Win 10 PC. I have assigned a static IP addresses to my PCs.
NameIP AddressSubnet MaskGateway
Hyper-V Host PC192.168.1.100255.255.255.0192.168.1.1
Win 10 PC192.168.1.201255.255.255.0192.168.1.1
 Router’s IP address:
To resolve this, I added manual DNS entries in my Win 10 PC. I assigned and as DNS servers in Win 10 PC. But I was not able to add client PC to domain. I had searched for the help on Internet but almost all the pages suggested, assigning correct IP address as my DNS server, which I had already done.
Hence I had to think something different to fix this issue. I decided to turn off IPv6 on my Win 10 Client PC's network adaptor (By default, this is enabled on all network adaptors). As soon as I had disabled IPv6, I was able to add Win 10 PC to my Domain controller.
Hope you find this article informative.

1 comment:

  1. Exactly what I was looking for. Thank you :-)