Adding an additional DC/DNS to existing domain

[Mik]

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??

thanks for any assistance!

Mik

 

[Dave Shaw [MSFT]]

That's really all there is to it.

If DNS isn't populating the zone, check for AD replication problems.

-ds

 

[Kurt]

And there may be the key: did you create the zone?

....kurt

 

[Hank Arnold]

That's exactly what I did when I added a DC to our domain.... As Dave
Shaw indicates, sounds like there may be a replication problem. Have you
checked the event logs?

Regards,
Hank Arnold

 

[Herb Martin]

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.

 

[Kurt]

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

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

 

[Herb Martin]

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?

Generally an existing AD integrated DNS zone just shows
up when DNS is installed but it seems to be less than 100%
consistent.

Surely some of those issue are due to failure to (fully) replicate
but there also may be some other anomolies.

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

...kurt

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

 

[Hank Arnold]

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

Regards,
Hank Arnold

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

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