Solved Unable to re-boot a VHD on win 7 pro 64bit

July 26, 2012 at 03:54:14
Specs: win 7 pro 64, 8
Hi,

I have created a Domain controller, dns and domain called ben.local

Right now I am on the client machine and try to set ben.local as the "member of the domain". I am getting this error:


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 "ben.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.ben.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.254

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

ben.local
local
. (the root zone)

Any idea why I have to do please? It is the first time I use active directory.

Thank you,


Ben


See More: Unable to re-boot a VHD on win 7 pro 64bit

Report •

#1
July 26, 2012 at 04:12:13
192.168.1.254 sounds like your router rather than your server. You should turn off DHCP on your router, and set your server to be a DHCP server, so that the information is picked up from the server. If you still want to use your router's DHCP, rather than the server's, you must configure it so that the DNS server it tells clients to use is your Windows server.

Alternatively, use manual addresses with the server as your DNS server.


Report •

#2
July 26, 2012 at 04:16:23
Thanks iJack,

I cannot disable the DHCP on this modem/router because it is blocked by the isp, instead I have entered manual IP for both my laptop and desktop pc(client and server).
But now the DHCP server will not be used anymore which is sad...


Report •

#3
July 26, 2012 at 23:12:03
✔ Best Answer
I'm not sure how the title relates to your problem, but all the same, I guess.

You probably have only one DC (which also plays the role of your DNS server).

Assuming you're not using DNS delegation, check your DNS on your DC [via Local Area Connection (LAC) properties]. It has probably reverted to a loopback (127.0.0.0/127.0.0.1).

Set your DC's DNS to the same static IP of your DC.

After that, log on to your client and set static DNS. Enter the DNS of your DC (which is also, again, your DC's IP).

Then try to join the computer to the domain.

Here's an example:
DC (Domain Controller):
LAC IP - 192.168.10.1
SM - 255.255.255.0
LAC DG - 192.168.10.254
LAC Preferred DNS Server - 192.168.10.1

CL (Client):
LAC IP - 192.168.10.2
SM - 255.255.255.0
LAC DG - 192.168.10.254
LAC Preferred DNS Server - 192.168.10.1

"I'm tired. But then again I'm so hungry I can't sleep. But what's the point of eating if your sleepy?" - Sniff, The Moomins.


Report •

Related Solutions

#4
July 27, 2012 at 02:20:48
Thank you for your help,

I have no idea why I have this title in my thread ??? Weird. This was created for another question.

Thank you for your help, I am going to try the above now.

Ben


Report •

Ask Question