Re: DNS Question
- From: "Paul Williams" <ptw2001@xxxxxxxxxxx>
- Date: Wed, 16 Aug 2006 20:21:43 +0100
That advise is dated and, I feel, only appropriate to certain circumstances.
I expect (hope) it to change with the release of any revised documentation
for SP2 or more likely, Longhorn.
Personally, if you have multiple DNS servers in the same physical site, I
would point them at each other for preferred and self as alternate.
However, this is mainly for two reasons:
1. Speedier start-up times due to the way initial-sync delays the DNS
service from reading the AD.
2. No errors in the event log re. the chicken and egg issue of AD-I DNS not
being able to read zone data from AD because AD hasn't started because it
can't query DNS because...
However, doing so does create network traffic. Some will argue that it is
always better to point to self and keep traffic local. That said, if you
point to self first it is almost pointless configuring an alternate as in
all liklihood, if DNS is down you have bigger problems. That being said, it
isn't quite pointless. : )
So, there's no definitive answer. It comes down to preference and
requirements. In single DC branch deployments you will always point to self
then core, however unlikely it is that core will be used.
There's also the argument for all DCs in a site using one or two DNS
servers. With AD-I zones I don't follow this advise.
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net
.
- References:
- DNS Question
- From: Robbert
- Re: DNS Question
- From: Jorge Silva
- DNS Question
- Prev by Date: Re: Lookup account based on SID
- Next by Date: Re: Question about security group
- Previous by thread: Re: DNS Question
- Next by thread: Re: DNS Question
- Index(es):
Relevant Pages
|
