Correct DNS setup order - Windows 2003

According to 291382. Can someone please explain what should be the best
configuration for my environment?

If I have the following setup (all Windows 2003 server)
DC1 - domain controller, DNS, DHCP
DC2 - domain controller and DNS
DC3 - domain controller and DNS
DC4 - domain controller

How should my DNS entries look like on the following:
DC1 - should point to itself first then DC2
DC2 - should point to DC1 then itself
DC3 - should point to DC1 then itself
DC4 - should point to DC1, then DC2

Would this be correct? What about the other servers and clients?

--
Eric Sabo
NT Administrator

Eric:

Good point. I looked through that KB article before. The
answer below isn't clear to me. I'd like to know if it
refers to AD integrated or standard DNS. For AD
integrated, I would think that pointing the DNS server to
itself for preferred DNS would be the way to go. Does
anyone have any comments on this? Thank you.

>Martin

Question: How do I set up DNS for other domain controllers
in the domain that are running DNS?
Answer: For each additional domain controller that is
running DNS, the preferred DNS setting is the parent DNS
server (first domain controller in the domain), and the
alternate DNS setting is the actual IP address of network
interface.

I don't know that there is any "hard-fast" rule.
Point them to each other "in a circle". Each should point to itself last.
When pointing to itself it may be better to use 127.0.0.1 so even if the NIC
is down it will still find the Service.

For example when there are only two each point to the other first, then to
itself. This was expressed to me by Product Support personally.

We didn't get into larger groups of DNS Servers, but I suspect to follow the
same logic it would go in a circle. Picture the machines standing in a
circle,..each points to the machine on the left and continues clockwise
around the circle and ends with itself using 127.0.0.1.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"MartinHTN" <(E-Mail Removed)> wrote in message
news:19ad301c44d61$f59ed490$(E-Mail Removed)...
> Eric:
>
> Good point. I looked through that KB article before. The
> answer below isn't clear to me. I'd like to know if it
> refers to AD integrated or standard DNS. For AD
> integrated, I would think that pointing the DNS server to
> itself for preferred DNS would be the way to go. Does
> anyone have any comments on this? Thank you.
>
> >Martin
>
> Question: How do I set up DNS for other domain controllers
> in the domain that are running DNS?
> Answer: For each additional domain controller that is
> running DNS, the preferred DNS setting is the parent DNS
> server (first domain controller in the domain), and the
> alternate DNS setting is the actual IP address of network
> interface.

microsoft recommends the pdc emulator fsmo role holder point to itself as
primary dns, and NO secondary entry. all additional DC's in the domian
should point to the PDC emulator as primary and themselves as secondary.


"Phillip Windell" <@.> wrote in message
news:(E-Mail Removed)...
> I don't know that there is any "hard-fast" rule.
> Point them to each other "in a circle". Each should point to itself last.
> When pointing to itself it may be better to use 127.0.0.1 so even if the
NIC
> is down it will still find the Service.
>
> For example when there are only two each point to the other first, then to
> itself. This was expressed to me by Product Support personally.
>
> We didn't get into larger groups of DNS Servers, but I suspect to follow
the
> same logic it would go in a circle. Picture the machines standing in a
> circle,..each points to the machine on the left and continues clockwise
> around the circle and ends with itself using 127.0.0.1.
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "MartinHTN" <(E-Mail Removed)> wrote in message
> news:19ad301c44d61$f59ed490$(E-Mail Removed)...
> > Eric:
> >
> > Good point. I looked through that KB article before. The
> > answer below isn't clear to me. I'd like to know if it
> > refers to AD integrated or standard DNS. For AD
> > integrated, I would think that pointing the DNS server to
> > itself for preferred DNS would be the way to go. Does
> > anyone have any comments on this? Thank you.
> >
> > >Martin
> >
> > Question: How do I set up DNS for other domain controllers
> > in the domain that are running DNS?
> > Answer: For each additional domain controller that is
> > running DNS, the preferred DNS setting is the parent DNS
> > server (first domain controller in the domain), and the
> > alternate DNS setting is the actual IP address of network
> > interface.
>
>

That sounds logical. Just hope the PDC Emulator doesn't get moved to a
different DC and then nobody remembers to readjust.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


<(E-Mail Removed)> wrote in message
news:UYkxc.13355$(E-Mail Removed) et...
> microsoft recommends the pdc emulator fsmo role holder point to itself as
> primary dns, and NO secondary entry. all additional DC's in the domian
> should point to the PDC emulator as primary and themselves as secondary.
>
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > I don't know that there is any "hard-fast" rule.
> > Point them to each other "in a circle". Each should point to itself
last.
> > When pointing to itself it may be better to use 127.0.0.1 so even if the
> NIC
> > is down it will still find the Service.
> >
> > For example when there are only two each point to the other first, then
to
> > itself. This was expressed to me by Product Support personally.
> >
> > We didn't get into larger groups of DNS Servers, but I suspect to follow
> the
> > same logic it would go in a circle. Picture the machines standing in a
> > circle,..each points to the machine on the left and continues clockwise
> > around the circle and ends with itself using 127.0.0.1.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "MartinHTN" <(E-Mail Removed)> wrote in message
> > news:19ad301c44d61$f59ed490$(E-Mail Removed)...
> > > Eric:
> > >
> > > Good point. I looked through that KB article before. The
> > > answer below isn't clear to me. I'd like to know if it
> > > refers to AD integrated or standard DNS. For AD
> > > integrated, I would think that pointing the DNS server to
> > > itself for preferred DNS would be the way to go. Does
> > > anyone have any comments on this? Thank you.
> > >
> > > >Martin
> > >
> > > Question: How do I set up DNS for other domain controllers
> > > in the domain that are running DNS?
> > > Answer: For each additional domain controller that is
> > > running DNS, the preferred DNS setting is the parent DNS
> > > server (first domain controller in the domain), and the
> > > alternate DNS setting is the actual IP address of network
> > > interface.
> >
> >
>
>

I wish Microsoft would give us this information in a technet article. Most
of the ones that I have read are not very clear in what they are saying.


<(E-Mail Removed)> wrote in message
news:UYkxc.13355$(E-Mail Removed) et...
> microsoft recommends the pdc emulator fsmo role holder point to itself as
> primary dns, and NO secondary entry. all additional DC's in the domian
> should point to the PDC emulator as primary and themselves as secondary.
>
>
> "Phillip Windell" <@.> wrote in message
> news:(E-Mail Removed)...
> > I don't know that there is any "hard-fast" rule.
> > Point them to each other "in a circle". Each should point to itself
last.
> > When pointing to itself it may be better to use 127.0.0.1 so even if the
> NIC
> > is down it will still find the Service.
> >
> > For example when there are only two each point to the other first, then
to
> > itself. This was expressed to me by Product Support personally.
> >
> > We didn't get into larger groups of DNS Servers, but I suspect to follow
> the
> > same logic it would go in a circle. Picture the machines standing in a
> > circle,..each points to the machine on the left and continues clockwise
> > around the circle and ends with itself using 127.0.0.1.
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "MartinHTN" <(E-Mail Removed)> wrote in message
> > news:19ad301c44d61$f59ed490$(E-Mail Removed)...
> > > Eric:
> > >
> > > Good point. I looked through that KB article before. The
> > > answer below isn't clear to me. I'd like to know if it
> > > refers to AD integrated or standard DNS. For AD
> > > integrated, I would think that pointing the DNS server to
> > > itself for preferred DNS would be the way to go. Does
> > > anyone have any comments on this? Thank you.
> > >
> > > >Martin
> > >
> > > Question: How do I set up DNS for other domain controllers
> > > in the domain that are running DNS?
> > > Answer: For each additional domain controller that is
> > > running DNS, the preferred DNS setting is the parent DNS
> > > server (first domain controller in the domain), and the
> > > alternate DNS setting is the actual IP address of network
> > > interface.
> >
> >
>
>

Does the order matter for member server or clients?



"Sabo, Eric" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> According to 291382. Can someone please explain what should be the best
> configuration for my environment?
>
> If I have the following setup (all Windows 2003 server)
> DC1 - domain controller, DNS, DHCP
> DC2 - domain controller and DNS
> DC3 - domain controller and DNS
> DC4 - domain controller
>
> How should my DNS entries look like on the following:
> DC1 - should point to itself first then DC2
> DC2 - should point to DC1 then itself
> DC3 - should point to DC1 then itself
> DC4 - should point to DC1, then DC2
>
> Would this be correct? What about the other servers and clients?
>
> --
> Eric Sabo
> NT Administrator
>
>