Re: Adding an additional DC/DNS to existing domain

That's the way it worked for me last month..... Of course, the existing DCs have to integrated DNS.....

Regards,
Hank Arnold

Kurt wrote:
So now I have a question. If you just install the DNS service on a new DC in an existing domain, wll the AD zone show up all by itself? Or do you have to create the zone manually and designate it as AD integrated, then wait for it to populate?

...kurt

"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message news:%234cBgeV4GHA.292@xxxxxxxxxxxxxxxxxxxxxxx
"Mik" <miked@xxxxxxxxxxxxxxx> wrote in message news:1159229207.540513.276430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I currently have 2 DCs which both have DNS (ADI zone) on them. I've
added another DC to the domain. Several weeks later I now want to
enable the 3rd DC to have DNS (be part of the existing ADI zone). Do I
simply go to add remove programs - add the DNS server ... and then
what...? After 20 minutes it still has no zone info in it.. ?? Do I
just need to be patient and it will self populate..? Do I need to
specify somewhere that this is ADI??


You didn't by any chance set the new DC to use ITSELF
as its own DNS Server (client NIC->IP properties) BEFORE
it replicated did you?

IF so, it would be unable to resolve the other DCs and therefore
replication would never occur. Once it replicates you may set
it to use itself which is usually the most efficient.

Run DCDiag on every DC and fix (or post) all FAIL, WARN,
and ERROR messages.


--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]

thanks for any assistance!

Mik




.

Relevant Pages

  • Re: Local Delivery is not sending to one recipient in Exchange Ser
    ... The DNS server was unable to open zone rickkochoil in the Active Directory ... Errors in File Replication Service: ... Running partition tests on: ForestDnsZones ...
    (microsoft.public.exchange.admin)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... Keep the zone with forest wide ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)
  • Re: Demoting a DC in W2003
    ... > were just promoted to DCs once the base OS was installed. ... > roles) and DC3 is a plain DC. ... > was configured to use itself as it's primary DNS server, ... due to replication problems that have been happening longer than 60 days ...
    (microsoft.public.win2000.active_directory)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... switch back to AD with Forest wide, and then put the DNS service ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... I did run dcdiag on all DCs, ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)
Loading