Join domain error
I'm a newbie and i hope my question is not to stupid.
We have a test envionment here with a 2008 server R2. This will act as Hyper V manager. On HyperV we have another 2008 R2 who should act as Domain COntroller and DNS. All the installations are completed without error.
We don't work with static IP and the DHCP is provided by the router.
After installation we cannot join our HyperV manager to the domain. We allways get this error.
An 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 "broeckx.com".The error was: "No records found for given DNS query."
(error code 0x0000251D DNS_INFO_NO_RECORDS)The query was for the SRV record for _ldap._tcp.dc._msdcs.broeckx.com
I know the problem is probably in the DNS but i just don't have a clue anymore at this point.
Can anyone help?
thnx
Answers
- You cannot use DHCP from your router if you are running Active Directory. All AD clients must use the DC for DNS.
Put you virtual machines in their own network. (I prefer a private virtual network isolated from the physical network). Give the DC a static IP in its own IP subnet. Install and authorize DHCP on the DC. Set up a scope (and activate it) to give AD clients IP addresses in the same IP subnet as the server and to use the DC for DNS.
Bill- Marked As Answer byJoson ZhouMSFT, ModeratorFriday, November 06, 2009 6:43 AM
Hi,
After you follow Bill’s suggestions, you can refer to the following KB article for troubleshooting if the issue persists:
How to verify that SRV DNS records have been created for a domain controller
http://support.microsoft.com/kb/816587
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer byJoson ZhouMSFT, ModeratorFriday, November 06, 2009 6:43 AM
All Replies
- You cannot use DHCP from your router if you are running Active Directory. All AD clients must use the DC for DNS.
Put you virtual machines in their own network. (I prefer a private virtual network isolated from the physical network). Give the DC a static IP in its own IP subnet. Install and authorize DHCP on the DC. Set up a scope (and activate it) to give AD clients IP addresses in the same IP subnet as the server and to use the DC for DNS.
Bill- Marked As Answer byJoson ZhouMSFT, ModeratorFriday, November 06, 2009 6:43 AM
Hi,
After you follow Bill’s suggestions, you can refer to the following KB article for troubleshooting if the issue persists:
How to verify that SRV DNS records have been created for a domain controller
http://support.microsoft.com/kb/816587
This posting is provided "AS IS" with no warranties, and confers no rights.- Marked As Answer byJoson ZhouMSFT, ModeratorFriday, November 06, 2009 6:43 AM
