Re: DNS error when installing second AD controller

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Don Williams (Don.Williams_at_cmoreNOSPAMmedical.com)
Date: 06/01/04 

Date: Tue, 1 Jun 2004 15:34:35 -0500

Thanks. I ran nltest /dsregdns on the first AD controller and the command
completed successfully. The AD wizard still will not install AD on the
second server. It fails with the same DNS error.

I ran netdiag dsgetdc on the second server which returned the following
error report:
DC discovery test. . . . . . . . . : Passed

    Find DC in domain 'pvm.local':

 This computer cannot be joined to the domain named [pvm.local]. This is
because the following DNS names (A records) could not be resolved : [p].
Ask your network/DNS administartor to add the A records for these computers
to DNS. By default these records should be dynamically registered in DNS by
the Domain Controllers. To debug why the DNS records are not registered in
DNS run dcdiag tool on the Domain Controller that failed such registration.
Use the command dcdiag RegisterInDNS.
        [FATAL] Cannot find DC in domain 'pvm.local'. [ERROR_NO_SUCH_DOMAIN]

    Find DC in domain 'CMORE':
    Found this DC in domain 'CMORE':
        DC. . . . . . . . . . . : \\PVMADC01
        Address . . . . . . . . : \\PVMADC01
        Domain Name . . . . . . : CMORE

    Find PDC emulator in domain 'CMORE':
    Found this PDC emulator in domain 'CMORE':
        DC. . . . . . . . . . . : \\PVMADC01
        Address . . . . . . . . : \\PVMADC01
        Domain Name . . . . . . : CMORE
        Flags . . . . . . . . . : PDC WRITABLE

However, dcdiag /test:registerInDNS completes successfully.

Why would this test attempt to locate an A record for a device named [p]?

Thanks for your patience and assistance.
  Don Williams

"Chriss3" <noSpamHere@chrisse.se> wrote in message
news:#pQ3GTBSEHA.3476@tk2msftngp13.phx.gbl...
> If you have Windows Server Support Tools installed, you can run the follow
> command line tool nltest with the syntax below
>
> nltest /dsregdns
>
> To register the current domain controller in dns again.
>
> --
> Regards
> Christoffer Andersson
>
> No email replies please - reply in the newsgroup
> ------------------------------------------------
> http://www.chrisse.se - Active Directory Tips
>
> "Don Williams" <Don.Williams@cmoreNOSPAMmedical.com> skrev i meddelandet
> news:%23AUz8fASEHA.1348@TK2MSFTNGP12.phx.gbl...
> > Thanks. I have verified that the second server is configured to use the
> > first server for DNA and correctly does name resolution for the address
of
> > the first server. It appears the the AD wizard is the only process that
> > can't find the address.
> >
> > "Chriss3" <noSpamHere@chrisse.se> wrote in message
> > news:#sxz2KASEHA.3944@TK2MSFTNGP11.phx.gbl...
> > > Make sure the TCP/IP DNS Settings on this second server points to the
> > first
> > > one so you are available to resolve the domain name correct. Active
> > > Directory is depending on DNS and can't work with out it,
> > >
> > > For more information see the link below:
> > >
> >
>
http://www.microsoft.com/technet/prodtechnol/windows2000serv/technologies/ac
> > tivedirectory/maintain/opsguide/part1/adogd10.mspx
> > >
> > > --
> > > Regards
> > > Christoffer Andersson
> > >
> > > No email replies please - reply in the newsgroup
> > > ------------------------------------------------
> > > http://www.chrisse.se - Active Directory Tips
> > >
> > > "Don Williams" <Don.Williams@cmoreNOSPAMmedical.com> skrev i
meddelandet
> > > news:epkD06$REHA.2496@TK2MSFTNGP11.phx.gbl...
> > > > When attempting to create a second Active Directory domain
controller
> in
> > > my
> > > > newly upgraded from NT4 W2K3 AD I receive the following error:
> > > >
> > > > "An Active Directory domain controller for the domain pvm.local
could
> > not
> > > be
> > > > contacted.
> > > > Ensure that the DNS domain name is typed correctly.
> > > > If the name is correct, then click Details for troubleshooting
> > > information."
> > > >
> > > > Opening Details results in the following:
> > > >
> > > > DNS was successfully queried for the service location (SRV) resource
> > > record
> > > > used to locate a domain controller for domain pvm.local:
> > > >
> > > > The query was for the SRV record for _ldap._tcp.dc._msdcs.pvm.local
> > > >
> > > > The following domain controllers were identified by the query:
> > > > pvmadc01.pvm.local
> > > >
> > > > 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.
> > > >
> > > > The new AD server points to pvmadc01.pvm.local for DNS.
> > > > I checked the A record for pvmadc01.pvm.local and it exists in DNS
on
> > the
> > > > first domain controller.
> > > > I can ping pvmadc01.pvm.local from the console of the new AD server.
> > > >
> > > > Any thoughts on what am I doing wrong? Thanks!
> > > >
> > > > Don Williams
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Relevant Pages

  • Re: Additional domain controller
    ... You mean the DNS is running on the second server without being configured? ... I have a W2K server that I intend to promote to a domain controller, ... My question is, should I remove the DNS services and then run DCPROMO, ...
    (microsoft.public.windows.server.sbs)
  • Re: DNS error when installing second AD controller
    ... The AD setup wizard is failing on the following DNS error: ... "An Active Directory domain controller for the domain pvm.local could not be ... -I can ping pvmadc01 and pvmadc01.pvm.local by name from the second server. ... Ethernet adapter Local Area Connection 2: ...
    (microsoft.public.windows.server.active_directory)
  • Adding second Windows 2003 domain controller
    ... My problem is adding a second Domain Controller. ... set up the DNS etc. ... The second server can. ... domain 5 The second server can be added to the firsts domain. ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS error when installing second AD controller
    ... Make sure the TCP/IP DNS Settings on this second server points to the first ... > "An Active Directory domain controller for the domain pvm.local could not ...
    (microsoft.public.windows.server.active_directory)
  • Re: Internet Access is slow as molasses....
    ... > to the DNS hierarchy to me? ... In an Active Directory environment DNS is where the Domain Controller stores ... If the Clients use the ISP's DNS they won't be ...
    (microsoft.public.win2000.dns)