Should a DC point to another DC as an Alternate DNS?

  • Thread starter Thread starter Hank Arnold
  • Start date Start date
H

Hank Arnold

We have two (soon to be 3 DC's) in our domain. I'm reviewing the setup and
one question came up. In each DC, I have it pointing to itself as the
Preferred DNS server. Should they be pointing to the other DC as an
"AlternateDNS Server"? Or will this cause problems??
 
Hank Arnold said:
We have two (soon to be 3 DC's) in our domain. I'm reviewing the setup and
one question came up. In each DC, I have it pointing to itself as the
Preferred DNS server.
Click to expand...

Generally (unless you have certain problems) this is correct.
Should they be pointing to the other DC as an
"AlternateDNS Server"? Or will this cause problems??
Click to expand...

Generally this is fine also. (We are assuming they are
both DNS servers.)

If these are "AD Integrated"...

In the beginning or if replication fails you must pick only
one to be the "Single master", and use Secondary for the
others until you get them registered with DNS and both
DNS and AD replicating.

During this time, they should (probably) all use JUST the
single master in their client properties.

Once everything is replicating, they can use themselves
(only or in combination) and all can be AD-Integrated
masters.
[/QUOTE]
 
Right. Both are running DNS, "AD Integrated" and the configuration of DNS is
identical. Replication is not a problem.... Thanks for the quick feedback...

Hank Arnold


Herb Martin said:
Generally this is fine also. (We are assuming they are
both DNS servers.)

If these are "AD Integrated"...

In the beginning or if replication fails you must pick only
one to be the "Single master", and use Secondary for the
others until you get them registered with DNS and both
DNS and AD replicating.

During this time, they should (probably) all use JUST the
single master in their client properties.

Once everything is replicating, they can use themselves
(only or in combination) and all can be AD-Integrated
masters.
Click to expand...
[/QUOTE]
 
No it will not cause problems, actually MS recommends you point them to
another DC..........However, consider two things;

1. pick a DC in your same site to cut down on WAN traffic
2. remember that any changes you make to an AD integrated zone will take
atleast 15 mins. to replicate and therefore won't be available till then.
 
rickiez said:
No it will not cause problems, actually MS recommends you point them to
another DC..........However, consider two things;
Click to expand...

I doubt that is a "general" recommendation -- although you might
have found someone said it once or so in some whitepaper or
article.

You may have seen some at Microsoft say this, but it isn't really
what "microsoft says." ( I believe I may have as well.)

It is generally WRONG in any case.
1. pick a DC in your same site to cut down on WAN traffic
Click to expand...

Each DC should generally point to itself if everything is working
properly -- and can quite reasonably add another DNS server second
by using first another DC in the same site then the others as desired.
2. remember that any changes you make to an AD integrated zone will take
atleast 15 mins. to replicate and therefore won't be available till then.
Click to expand...

And longer across Sites (in most environments.)
 
Back
Top