An Active Directory Domain Controller (AD DC) for the domain "mydomain.LAN " contacted. Ensure that the domain name is typed correctly. If the name is correct, click Details for troubleshooting information. When I click on details I see the following message. The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AC DC) for domain "mydomain.LAN ". 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.mydomain.LAN 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.10.1 192.168.1.1 - One or more of the following zones do not include delegation to its child zone: mydomainname .LAN LAN (the root zone) I'm not sure how to fix this issue.

This error is common when your client's DNS settings are incorrect. For all of the computers on the internal network that are joining the domain, make sure their DNS settings are pointing to the intranet DCs which are most likely hosting DNS. If you clients are DHCP enabled, make sure the settings in the DHCp scope are correct. If this is a small office/ home office (SOHO) network, and you are using a router for DHCP, you may need to disable those services and enabled them on one or more of your Windows servers. If you would like, please post the results of IPCONFIG /all from your client. Visit: anITKB.com, an IT Knowledge Base.

Thank you for the response. I will post the results of the ipconfig /all. Emil H. Kahihikolo

Here's the ipconfig /all from one of the workstations. Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Recept>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : FrontDesk Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek PCIe FE Family Controller Physical Address. . . . . . . . . : 64-31-50-1C-06-00 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::3d0f:e4a1:dcca:c195%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.1.113(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : Sunday, February 27, 2011 5:17:38 PM Lease Expires . . . . . . . . . . : Monday, February 28, 2011 5:17:38 PM Default Gateway . . . . . . . . . : 192.168.1.1 DHCP Server . . . . . . . . . . . : 192.168.1.1 DHCPv6 IAID . . . . . . . . . . . : 265586020 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-14-98-A6-B2-D4-85-64-C0-BF-89 DNS Servers . . . . . . . . . . . : 192.168.1.1 10.1.10.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{28E9F2FD-70B8-4ACF-B8EE-C35BF359B77D}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Local Area Connection* 9: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:5a:19f5:3f57:fe8e(Prefer red) Link-local IPv6 Address . . . . . : fe80::5a:19f5:3f57:fe8e%10(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : DisabledEmil H. Kahihikolo

I noticed that your Default Gateway and DHCP Server has the same IP. I also noticed that your primary DNS server is also this IP (192.168.1.1). Is this a Router? If so, are you able to modify the DHCP scope so that your clients point their DNS settings to an internal DNS server instead? If clients point to a router that is simply running DNS proxy services, the router will receive the DNS query for the domain, and simply foward the request to one of the DNS servers in the ISP's network. Of course, neither system will be able to resolve queries for your domain. That is why it is important to configure your internal hosts correctly. Designing Active Directory for a SOHO Network http://www.anitkb.com/2010/12/designing-active-directory-for-soho.html I would recommend a design closer to something like this example.... Visit: anITKB.com, an IT Knowledge Base.

Is the device 192.168.1.1 a router or the DC? If you want to join to a domain, please make sure that the DNS server for the client is the domain DNS server. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”