"Best" is a troublesome word in this case.
"TRock" <TRock[ at ]discussions.microsoft.com> wrote in message
news:368240AB-1F57-4880-8C5C-9E9C71D8EAFD[ at ]microsoft.com...
[Quoted Text] > Three location scenario with trusted domains running 2003 DC and DNS.
>
> Location/domain A: abc.com
> Location/domain B: xyz.com
> Location/domain C: 123.com
>
> Users from each of these domains frequently travel/work between the sites
> and need to be able to resolve names from thier own domain AND from the
> others.
>
> At present, each location/domain has its own DNS server and there are
> secondary zones created for the other locations/domains.
That works and is a good solution if the zones are not particularly large
nor changing frequently. (Stubs are similar but not necessary in these
cases.)
An (almost equal to stubs) alternative is Conditional Forwarding but
there is seldom a significant difference between these two choices
even though there is a subtle TECHNICAL difference that affects
a few networks.
Secondaries are your only real choice IF you have Win2000 DNS
servers.
> Is this the best way to set this up, or should I be using conditional
> forwarders to accomplish this? Or some other method?
Another choice, perhaps the "best" even, is using Forest Wide DNS-DC
scope for AD Integrated DNS as long as it is all one Forest with only
Win2003 DCs.
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
|