DNS windows 2003 question

  • Thread starter Thread starter Marcel
  • Start date Start date
M

Marcel

Hello NG



DNS windows 2003 question



I have setup a Root domain with one child called root.local and
child.root.local

Is it correct tat I hav eto do two domain to setup one root.local that have
a delegation to childe.root.local? Or what is the best? Also do I have to do
a sedentary Zone on every DC on the child from from root.local? Or is it
enough that I do a sub zone?



What is the best configuration to use AD integration zone.



Thanks a lot



Marcel
 
I have setup a Root domain with one child called root.local and
child.root.local

Is it correct tat I hav eto do two domain to setup one root.local that have
a delegation to childe.root.local?
Click to expand...

Question above is unclear....If you asked, "Must I delegate the the DNS zone
too?" then the answer is yes.
Or what is the best? Also do I have to do
a sedentary Zone on every DC on the child from from root.local? Or is it
enough that I do a sub zone?
Click to expand...

Normal is to actually do the Secondary (rather than SubDomain) as the
subdomain
requires much unnecessary manual configuration every time the child changes.

Alternatives (Win2003 Only): Use Stub Zones or Conditional forwarding to
substitute
for Secondary zones on "other domain."
What is the best configuration to use AD integration zone.
Click to expand...

Another alternative, use AD Integrated and setup replication to flow across
Domain barriers (based on Forest or custom Partition for DNS)
 
You don't necessarily have to have two domains. Not sure if you are talking about two AD domains or two DNS domains. AD
can be installed into child.root.local without having to have AD in the root.local domain. Also, in DNS you don't necesarily have
to have root.local in order to have child.root.local. You could certainly have just a AD and DNS domain called child.root.local
without any problems. In this case, child.root.local wouldn't technically be a child. It would be it's own autonomous domain.

In order to provide the best configuration here, we'd need much more information. If you have a simple setup with a single
location and no need for multiple domains, just create a root.local domain and put everything there. If you have a more complex
organization, then use root.local as a root domain and create child domains for large remote sites. Again, this all depends on
your organization's work flow.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
Back
Top