Re: Best DNS Ordering Practice for Two Domain Controllers One Domain

"W" <> wrote in message
news: ...
> Say you have two Windows 2003 domain controllers in a single domain
> forest.
> Let's call them DC1 on IP1 and DC2 on IP2.
>
> DC1 has its DNS specified in its IP setup in order as:
>
> IP1
> IP2
>
> My question is what is the preferred IP ordering for DNS on DC2? Should
> DC2 always point to itself as the primary DNS, or should all domain
> controllers always point to a single master domain controller as the
> primary?

There is a debate as to if it should be

1. itself
2. the other one

OR

1. the other one
2. itself


I use the second option.

1. the other one
2. itself

On bootup it can be faster if the machine sees a live DNS without having to
wait for it's own DNS Services to "come up".

Others will have other opinions.

In the end,...both ways work.


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

On Wed, 5 May 2010 14:34:23 -0700, "W" <>
wrote:

>"Phillip Windell" <> wrote in message
>news:...
>> "W" <> wrote in message
>> news: ...
>> > Say you have two Windows 2003 domain controllers in a single domain
>> > forest.
>> > Let's call them DC1 on IP1 and DC2 on IP2.
>> >
>> > DC1 has its DNS specified in its IP setup in order as:
>> >
>> > IP1
>> > IP2
>> >
>> > My question is what is the preferred IP ordering for DNS on DC2?
>Should
>> > DC2 always point to itself as the primary DNS, or should all domain
>> > controllers always point to a single master domain controller as the
>> > primary?
>>
>> There is a debate as to if it should be
>>
>> 1. itself
>> 2. the other one
>>
>> OR
>>
>> 1. the other one
>> 2. itself
>>
>>
>> I use the second option.
>>
>> 1. the other one
>> 2. itself
>>
>> On bootup it can be faster if the machine sees a live DNS without having
>to
>> wait for it's own DNS Services to "come up".
>
>I'm going with your method if all things are about equal, simply to get the
>faster bootup.


As Phillip said, it's mixed regarding opinions. I actually prefer
itself first, and another DC as second. I find it boots fine either
way.

If in a scenario where there's only one DC/DNS at a remote location,
you definitely want to set itself as first.

Ace

This posting is provided "AS-IS" with no warranties or guarantees and confers no rights.

Please reply back to the newsgroup or forum for collaboration benefit among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services

If you feel this is an urgent issue and require immediate assistance, please contact Microsoft PSS directly. Please check http://support.microsoft.com for regional support phone numbers.

"W" <> wrote in message
news: ...
> I'm going with your method if all things are about equal, simply to get
> the
> faster bootup.

Sounds good. But sometimes you want to go the other way if the other DC is
over a WAN and you can't guarantee that it will be dependably
reachable,...in that case use the first example. Either way you will be
alright.


--
Phillip Windell

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------