Archived from groups: microsoft.public.win2000.dns (
More info?)
> all ad and dns data appears to have replicated successfully i just need
> to know as I have my primary dns pointing at its self should the
> secondary also point to the primary or itself?? and shoult the primary
> remain pointing to itself?
>
The generally correct (and most efficient) answer is that every
DC points to itself first, and to the other (nearby) DCs which
hold the same info second, third etc. -- unless there is a positive
reason not to do this in a specific case.
You will hear some "old wives tale"-like recommendation to
point each DC to the other but this based on a troubleshooting
scenario where doing so temporarily may solve a problem
created by a perfectly correctly misconfiguration issue, and
even in that specific case they really should ALL point to the
Primary (or most favored Primary if AD Integrated DNS).
We do this temporarily when the DCs are not all registered
in the database correctly -- once they are all properly
registered we can use the most efficient settings:
self-first, other nearby DNS server next
The one real case where a DNS should not point to itself
(I have one of these) is when the DNS server is NOT an
internal DNS server for your network (e.g., running on
a Proxy/firewall box) but it is a domain member and so
needs that internal information.
So we can amend our rule to say: An internal DNS (i.e.,
one which holds internal records AND uses those internal
records) should point to itself first.
This should practically always be the case for a DC-DNS
so we can likely leave out this overly-pedantic exception.
(My firewall-proxy DNS server is NOT holding the domain
or other internal records, nor is it a DC.)
Ultimately the only rule that is really inviolable is that ANY
DNS client should point to the DNS servers that can answer
the questions to which it needs answers.
Then it is generally the case that it should point to the nearest
(in terms of network speed and efficiency) first.
A DC or even a DNS server is also such a "DNS client" in
almost all cases.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
"pscyime" <pscyime.1r0a2a@> wrote in message
news:Jaednd5UepemVyXfRVn_vg@giganews.com...
>
> hi all knowig ones!!
>
> well here i am agai gents and ladies
>
>
> I have just added a second dc to my home lan both runing the domain
> mydomain.local
>
> now i have also added the dns role to the second dc , created a
> secodary zone which points at the original server to get its zone info
>
> all ad and dns data appears to have replicated successfully i just need
> to know as I have my primary dns pointing at its self should the
> secondary also point to the primary or itself?? and shoult the primary
> remain pointing to itself?
>
> any help is greatly appreciated as always
>
> regards
>
> si
>
>
> --
> pscyimePosted from http://www.pcreview.co.uk/ newsgroup access
>
Facebook
Twitter
Instagram