Can't join domain

	Home \| Site Map \| How To \| Windows Vista \| Case Studies \| Articles \| Forums \| Services \| Donations \| Careers \| About Us \| Contact Us\|

"A domain controller for the domain could not be contacted"

"DNS name does not exist", "error code 0x0000232B RCODE_NAME_ERROR"

"The DNS SRV records required to locate a domain controller for the domain are not registered in DNS"

Situation: The client has a domain network and DC, DNS and DHCP is on a Windows 2000 server. There are 20 XP client joined the domain without any problems. Recently, they just add one Windows 2003 but can’t join the domain with this message: “A domain controller for the domain could not be contacted”. The dcdiag.txt has this message:

“The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain chicagotech.net:

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.abc.local

Common causes of this error include the following:

- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:

192.168.0.5

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

chicagotech.net

local

. (the root zone)"

Troubleshooting:

1. We logon as the administrator with the same password on both servers.

2. Server 2003 can ping DC by IP, host name and FQDN.

3. The DC – server 2000 can ping the server 2003 by IP and host name but not FQDN.

4. Use nslookup on both servers and it seems work fine. Nslookup points to correct default server which is DC – server 2000.

5. No firewall and any security software on both servers except anti-virus software.

6. No errors in DNS and System Event viewer on both servers.

7. The server 2003 hasn't registered A record on DNS.

8. DHCP Client is running.

Problem and solution: Finally, we found the DNS missed 4 SRV records, _msdcs, _sites, _tcp and _tdp. Running "netdiag /fix" on the Win 2k DC solved the problem.