Cannot Promote Second Domain Controller

  • Thread starter Thread starter Tiffany
  • Start date Start date
T

Tiffany

I am trying to promote a server to be a second domain
controller for my brand new domain. I added the SRV
records to the DNS on the domain controller. Received
error "The specified domain controller either does not
exist or could not be found". When I used NSLOOKUP to
see if the SRV record exists, it tells me that it cannot
find my domain controller. What should I do next? Thank
you very much.
 
Easy fix.

Yep, on the second machine setup it to point to your 1st DC for DNS
resolution. Then make sure the DNS zone you've created for your domain is
setup to accecpt DYNAMIC UPDATES.
 
In
Tiffany said:
I am trying to promote a server to be a second domain
controller for my brand new domain. I added the SRV
records to the DNS on the domain controller. Received
error "The specified domain controller either does not
exist or could not be found". When I used NSLOOKUP to
see if the SRV record exists, it tells me that it cannot
find my domain controller. What should I do next? Thank
you very much.
Click to expand...

What do you mean by "I added the SRV records to the DNS on the domain
controller."
The SRV records should have been created by the DC when it was promoted, if
it is pointed to the internal DNS.

Verify that all domain members and DCs are pointing only to the internal DNS
server for the AD domain. No ISP's DNS allowed.

If you have further problems post back with the ipconfig /all AND the AD
domain name from the current DC and the one your are trying to add. So that
we can diagnose the problem and verify this is not a disjointed name space.
 
In
Tiffany said:
I am trying to promote a server to be a second domain
controller for my brand new domain. I added the SRV
records to the DNS on the domain controller. Received
error "The specified domain controller either does not
exist or could not be found". When I used NSLOOKUP to
see if the SRV record exists, it tells me that it cannot
find my domain controller. What should I do next? Thank
you very much.
Click to expand...

Just to add to the other responses about the nslookup message (yes, just a
message and NOT an error), upon intialization, it's just trying to tell you
what your DNS server's IP address name is by looking in your reverse zone.
If the DNS server's IP address does not have a PTR entry, or if you do not
have a reverse zone created for your IP subnet, it will give you that
"message" (once again, not an error), that it cannot find the name of it.
That's it. Subsequent commands will work with no probs.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top