Networks

Ask something
Question Locked

Unable to add a new AD Domain Controller

0 helpful
4 replies

by d.elder

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Here's the run down:
Currently running an NT domain.
Promotted a back NT 4.0 server to PDC (PC name: Domain-BU3).
Removed that from the network and put it on its own hub, also on that hub is a stand alone 2003 server (no roles setup on it, PC Name: Domain-BU2).
Upgraded the Win NT 4.0 PDC to Windows Server 2003.
The upgrade seemed to work just fine, it is now the AD DC and DNS server. We'll call the domain name NETWORK.org (the NT domain name was NETWORK)
Booted the Win 2003 server and it was able to join the AD Domain and recognized it as such.
Both machines can see each other on the domain.

Here's the problem, we are attempting to turn on Domain-BU2 as an additional domain controller.

I pull up the AD installation wizard.
Mark it under "Additional domain controller for an existing domain", click Next
It already has the Domain name filled with NETWORK.org, enter the administrator user name and password, click Next.
Then it gives me a message:
"An Active Directory domain controller for the domain NETWORK.org could not be contacted.

Ensure that the DNS domain name is typed correctly.

If the name is correct, then click Details for trouble shooting"

The details show this as the error message:
"DNS name does not exist"
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc_msdcs.NETWORK.org

Then it lists the DNS server IP address that DOMAIN-BU2 is configured to go to, which is correct, xx.xxx.xx.119

Then, one or more of the following zones do not include delegation to its child zone:

NETWORK.org
org
. (the root zone)

If I change the Domain name to just NETWORK and click Next, it allows it to go to the next screen where it asks to enter the full DNS name of the existing domain.
if I click Browse I can see the NETWORK.org domain and select it, however I get the same error and details that the previous screen does.

HELP!

Still realitively new to AD, we want to be sure we can get this to work in this test environment before we do this on the live network.

4 replies

by d.elder

Obviously this is because it can't resolve the DNS server.
When we do an nslookup on domain-bu3 (the AD DC and DNS server), it knows the DNS server is at IP address XX.XXX.XX.119, but it can't find the server name. I've gone into DNS mgr and tried adding a reverse lookup to a PTR but it is still unable to resolve that name.

I'm sure I'm just missing something simple but not finding anything that jumps out in the MS articles.

by d.elder

Turns out it was indeed the PTR in the Reverse Lookup of the DNS.
We removed the one that was created automatically and manually created a new one, however we were impatient.

When I got back in this morning everything was working fine. We thought we'd set all appropriate TTL to 1 s, but there must have still be one set to 1h (we made the changes at 10 to 5 on Friday).

The plan to crush the NT domain under the wheels of AD will commence.

This discussion is closed to new replies.