An Active Directory Domain Controller to the domain .... could not be contacted

0

I got this error:

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 "mydomain.com":

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.com

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.1

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

mydomain.com
com
. (the root zone)

I have active directory setup on a windows 2008 server (home setup 2 computers, server mentioned above and windows 10 desktop) the host computer is connected to the domain without issue. A client computer can access the server, and all its resources, however cannot log into the domain this is the error I get. DNS resolves to the correct IP, router setup to direct traffic to that IP. Tried DMZ, just to test no change, edited hosts file to point to internal network IP rather than WAN IP no change.

Web Service, SFTP, File sharing all work remotely and locally however cannot get my local computer to connect to the domain. Researched the internet heavily, none of the solutions have worked. I have a feeling I'm missing something simple.... anyone?

active-directory
domain
domain-controller
asked on Server Fault Aug 12, 2015 by CaptKA-nuckles • edited Aug 25, 2015 by Falcon Momot

1 Answer

5

The DC/DNS server should use it's own ip address for primary DNS and should use 127.0.0.1 for secondary DNS (assuming a single DC/DNS server).

The clients should use the DC/DNS server for DNS.

You can configure the DNS server properties to use the Forwarders of your choice to resolve external DNS names.

answered on Server Fault Aug 12, 2015 by joeqwerty

User contributions licensed under CC BY-SA 3.0