Home | Troubleshooting |  Quick Setup  |  Cisco How to  |  Data Recovery  |  Forums   | Blog | IT Exam Practice | Services  | About Us | Chicagotech MVP  | Search  | Contact Us  |                  Laptop for rent: $35 per day plus $10 for additional day

rental
 

 

* "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

Resolution 1: Fixing the DNS Issues

Since the DC – server 2000 can ping the server 2003 by IP and host name but not FQDN, we check the DNS records and find that the server 2003 hasn't register itself in the DNS records. Then we add A record and PRT manually. Still, we can't join the server 2003 to the domain.

After study the DNS settings carefully, we find there are not SRC records (_msdcs, _tcp, _udp and _sitesin) the DNS. According Microsoft, the SRV records may be missing in the DNS Management console or database if  the following conditions exist:

The DNS server is configured as a Dynamic Host Configuration Protocol (DHCP) client.

The DNS zone has a name other than your Active Directory domain name.

The zone is not enabled to allow dynamic updates.

Then we use  netdiag /fix command on the domain controller to create those 4 SRV records. The server 2003 registers on the DNS records and joins the domain successfully.
 

Post your questions, comments, feedbacks and suggestions

Contact a consultant

Related Topics

Previous Page   Next Page
 

 


 

 

Hit Counter   This web is provided "AS IS" with no warranties.
Copyright © 2002-2018 ChicagoTech.net, All rights reserved. Unauthorized reproduction forbidden.