• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 257
  • Last Modified:

2003 Server cannot find DC

I am upgrading a 2003 Server to a DC.  The 2000DC has been prepped with adaprep...  The 2003 server is on 192.168.101.x scheme and the 2000 DC is on a 172.16.1.x scheme.  When running DCpromo I get the following:

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain HMI-INC.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.HMI-INC.COM

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:

172.16.1.232
172.16.1.231
192.168.101.241
192.168.101.231

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

HMI-INC.COM
COM
. (the root zone)


DNS is my weak point (well, one of them)...what do I have to add to the 2000 DNS server's DNS?
0
ikeepon
Asked:
ikeepon
1 Solution
 
NJComputerNetworksCommented:
This (windows 2003) computer is configured to use DNS servers with following IP addresses:

172.16.1.232
172.16.1.231
192.168.101.241
192.168.101.231


Change this to point to the Windows 2000 DC/DNS server's IP address.  Then retry DCPROMO.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

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