Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 805
  • Last Modified:

DNS Error joining Windows 7 to Server 2000 domain

Hi, and thanks for any insight you can offer.

I have a client on a Windows 2000 domain, and they're currently upgrading their PCs and then their server to 2012.  In the meantime, for an accounting system upgrade that will precede the sever upgrade, I'm joining a few of the Windows 7 Pro PC's onto the domain to test the new software.

One of the PCs joined just fine, but I'm having trouble with another one of them.  I can't get pas t a DNS error that is thrown every time I try to join the domain.  The error is below and attached:

I;ve tried several time, and am now at a loss.

Does anyone have an idea how to get past this?
************************************************
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 "HANSON.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.HANSON.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.254.254

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

HANSON.LOCAL
LOCAL
. (the root zone)
0
mlitin
Asked:
mlitin
1 Solution
 
bmurray-vbCommented:
Set a static IP address on the problem machines on the subnet that the domain controller resides that doesn't interfere with the existing DHCP scope.  Make sure the only DNS server configured on the machine is the domain controller then try it again.
0
 
mlitinAuthor Commented:
Thanks so much,

Hardcoded the DNS and IP, and all was good.  Duh....
0

Featured Post

Lessons on Wi-Fi & Recommendations on KRACK

Simplicity and security can be a difficult  balance for any business to tackle. Join us on December 6th for a look at your company's biggest security gap. We will also address the most recent attack, "KRACK" and provide recommendations on how to secure your Wi-Fi network today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now