dcpromo fails on 2nd server after in-place upgrade of NT to W2K3

After completing an in-place upgrade of our NT 4 PDC to Windows 2003 Server,
I cannot run dcpromo to create a second domain controller on a server running
Windows 2003. I am getting a DNS error that seems pretty common but I haven’t
been able to solve it. I am hoping someone can see what it is I am missing.

Below is the pasted error I get when running dcpromo as well as some output
from the nltest utility.

The Active Directory name (and DNS zone) is MyDomain.com and the NetBIOS
name of the domain is MyDomain.

I have correct SRV records for MyDomain.com (or so I think) for the upgraded
PDC under the MyDomain.com DNS zone. The upgraded PDC also has an “A”
record. The zone is Active Directory Integrated.

I am able to log into the domain, add computer and user accounts. The
remaining NT 4 BDCs continue to do their BDC thing. I can ping the upgraded
PDC by NetBIOS name, and by FQDN.

I get this output when I run nltest on the W2K3 member server I am trying to
dcpromo.

C:\ >nltest /dclist:mydomain.com
Cannot find DC to get DC list from.Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN

C:\ >nltest /dclist:mydomain
Domain 'mydomain' is pre Windows 2000 domain. (Using NetServerEnum).
List of DCs in Domain mydomain
\\myPDCemulator (PDC)
\\myBDC1
\\myBDC2

Here is the output of nltest when I run the command on the upgraded PDC:

C:\ >nltest /dclist:mydomain
Get list of DCs in domain 'domain' from '\\MYPDCEMULATOR'.
mypdcemulator.mydomain.com [PDC] [DS] Site: Default-First-Site-Name
BDC1
BDC2
BDC_BAK

C:\ >nltest /dclist:mydomain.com
Get list of DCs in domain 'mydomain.com' from '\\mypdcemulator.mydomain.com'.
mypdcemulator.mydomain.com [PDC] [DS] Site: Default-First-Site-Name
BDC1
BDC2
BDC_BAK

Here is the error message I receive after putting in my username, password
and domain name and click next. (using an account with Enterprise Admin
membership)

Using “mydomain” in the domain name field (without quotes):
_________________

Details:

The domain name mydomain might be a NetBIOS domain name. If this is the
case, verify that the domain name is properly registered with WINS.

If you are certain that the name is not a NetBIOS domain name, then the
following information can help you troubleshoot your DNS configuration.

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

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.mydomain

Common causes of this error include the following:
__________________



Here is the error I get using “mydomain.com” in the domain name field
(without the quotes).
__________________
An Active Directory domain controller for the domain mydomain.com could not
be contacted. Ensure that the DNS domain name is typed correctly. If the
name is correct, then click Details for troubleshooting information.

Details:

DNS was successfully queried for the service location (SRV) resource record
used to locate a domain controller for domain mydomain.com:

The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.com

The following domain controllers were identified by the query:

myPDCemulator.mydomain.com

Common causes of this error include:

- Host (A) records that map the name of the domain controller to its IP
addresses are missing or
- contain incorrect addresses.

- Domain controllers registered in DNS are not connected to the network or
are not running.

For information about correcting this problem, click Help.
____________________

Thanks in advance for any guidance you can offer!

.

Relevant Pages

  • Intersite Replication Problem
    ... primary and secondary domain controllers. ... I installed the PDC and ... An Active Directory domain controller for the domain example.com ... Ensure that the DNS domain controller is typed ...
    (microsoft.public.win2000.general)
  • Re: NT to 2003 domain upgrade - DNS related question
    ... running W2K3 on it as an upgrade, it will automatically assume the "PDC ... promo the new box to PDC, and THEN do the in-place upgrade. ... The problem is that you're going to lose your DNS server if you do plan B ...
    (microsoft.public.windows.server.migration)
  • NT4 to 2k3 in place upgrade rollback problems
    ... first BDC and promoted one of the new BDC's to a PDC. ... that PDC to 2k3 and AD adding DNS to the new DC during the upgrade. ... Then we turned back on the original PDC and 1st BDC in our NT4 network. ...
    (microsoft.public.windows.server.migration)
  • Re: Promote Server to Domain Controller
    ... > Controller and then deactivate the Windows 4.0 Domain Controller? ... The only viable and safe way to upgrade the network is to: ... The only NT4 server that can be upgraded is the PDC, ... netbios domain model to a dns hierarchical architecture. ...
    (microsoft.public.win2000.general)
  • Re: Promote Server to Domain Controller
    ... > Controller and then deactivate the Windows 4.0 Domain Controller? ... The only viable and safe way to upgrade the network is to: ... The only NT4 server that can be upgraded is the PDC, ... netbios domain model to a dns hierarchical architecture. ...
    (microsoft.public.windows.server.setup)
Loading