Setting up two DC's config

  • Thread starter Thread starter Clifford
  • Start date Start date
C

Clifford

What should DNS entries be (and on which servers) when
adding a second DC to a domain?

At this point the member server I want to add as DC
cannot become an additional DC because it cannot contact
the current PDC for some strange reason. I get a error
saying that there is no valid PDC for my domain, or the
domain is incorrectly configured.

How do I resolve this situation?

Thank you.
 
The entries required for a DNS server are A, NS and SOA.
It also sounds like you may have a problem with the PDC Emulator FSMO role.
Check which machine holds this role and make sure it can be contacted.
 
First check, that DNS is live and running on your AD server. Make sure, that
all clients and servers point their DNS settings to your internal DNS
server. To verify, that your DC is functioning properly run dcdiag and
netdiag from support tools (they are on your Windows 2000 Server CD-ROM).
To see which records should be present in your DNS server look into
%systemroot%\config\netlogon.dns file. Check the content of the file with
your DNS server.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), Windows MVP
(e-mail address removed)
http://ladava.com
 
-----Original Message-----
First check, that DNS is live and running on your AD server. Make sure, that
all clients and servers point their DNS settings to your internal DNS
server. To verify, that your DC is functioning properly run dcdiag and
netdiag from support tools (they are on your Windows 2000 Server CD-ROM).
To see which records should be present in your DNS server look into
%systemroot%\config\netlogon.dns file. Check the content of the file with
your DNS server.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), Windows MVP
(e-mail address removed)
http://ladava.com




.
Click to expand...
Thank you for your reply....

DCDIAG compains that the GUID DNS name could not be
resolved to an IP address. What DNS record is being
referred to here? It goes on to say that although the
GUID DNS name could not be contacted, the server name
(netbios name) could be resolved, and pinged.

The intersite check passes, as well as the fsmocheck

Please advise.

Thank you
 
Is your server pointing to your internal DNS server ? Post your ipconfig
/all from your server. This is probably the one installed on your Domain
controller. Open DNS snapin and verify that you have entries under your
domain zone. The entries should be the same as in
%systemroot%\config\netlogon.dns file. Check your dns zone properties that
you have enabled dynamic updates.
DNS GUID is located in _msdc folder under your domain in your DNS server. It
is a cname record.

--
Regards

Matjaz Ladava, MCSE (NT4 & 2000), Windows MVP
(e-mail address removed)
http://ladava.com
 
My server is now pointing to the internal DNS server yes.

ipconfig /all displays the IP of my PDC as the only DNS
server.

I have 4 entries under my domain and 4 folders listed as
well. These had to be configured automatically, as I did
not enter any data there.

I have no netlogon.dns file in %systemroot%\config - mine
is in %systemroot%\config\system32 There are a lot of
entries in that file that are not listed in my DNS snap-
in.

I have allowed dynamic updates.

However, i've started dcpromo to check if I can bring up
the server as a DC, and it works fine now. I'm currently
setting up my ex member server as an additional DC. My
PDC even passes all dcdiag tests but one - kccevent. What
test is this, and should I be concerned?

Thank you very much for your time and help!!
 
Back
Top