Child Domain DNS

[Dave Clark]

We are working on planning out our AD roll out and have
played with a test senario of a single forest and
multiple domains. When we setup the root DNS, it went
well and all setup great.

When setting up the child domain, it did create the "sub
domain" in the DNS structure as desired on the ROOT DNS
servers.

How would be the best way to either delegate control of
that child domain to the DCs for that child domain? Would
this be smart? Also, what about our outlaying sites
within this child domain taht will be GCs? Shouldn't
they have a copy of the AD DNS to keep traffic local? If
so, what would be the best way to accomodate that?

 

[Danny Sanders]

See:
HOW TO: Create a Child Domain in Active Directory and Delegate the DNS
Namespace to the Child Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;255248





and



How to create and configure an Active Directory Site in Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;318480







hth

DDS W 2k MVP MCSE

 

[Ace Fekay [MVP]]

In

We are working on planning out our AD roll out and have
played with a test senario of a single forest and
multiple domains. When we setup the root DNS, it went
well and all setup great.

When setting up the child domain, it did create the "sub
domain" in the DNS structure as desired on the ROOT DNS
servers.

How would be the best way to either delegate control of
that child domain to the DCs for that child domain? Would
this be smart? Also, what about our outlaying sites
within this child domain taht will be GCs? Shouldn't
they have a copy of the AD DNS to keep traffic local? If
so, what would be the best way to accomodate that?

Best way is to delegate it from the parent's DNS server(s) to the child's
DNS server(s). Then in the child's DNS server(s), set a forwarder back to
the parent. From the parent DNS, set a forwarder to the ISP. This way
resolution will work throughout the infrastrucuture and you get efficient
Internet resolution.

Here's more info on delegation:

255248 - HOW TO Create a Child Domain in Active Directory and Delegate the
DNS Namespace to the Child Domain:
http://support.microsoft.com/?id=255248


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Dave Clark]

Thanks for all the info....

 

[Ace Fekay [MVP]]

In

Thanks for all the info....

No prob.

Happy Holidays!


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Kevin D. Goodknecht [MVP]]

In Dave Clark <[email protected]> posted a question
Then Kevin replied below:
: We are working on planning out our AD roll out and have
: played with a test senario of a single forest and
: multiple domains. When we setup the root DNS, it went
: well and all setup great.
:
: When setting up the child domain, it did create the "sub
: domain" in the DNS structure as desired on the ROOT DNS
: servers.

If the Child DCs are using the parent DCs for DNS you have to manually add
the child zone.

:
: How would be the best way to either delegate control of
: that child domain to the DCs for that child domain? Would
: this be smart? Also, what about our outlaying sites
: within this child domain taht will be GCs? Shouldn't
: they have a copy of the AD DNS to keep traffic local?

Yes.

: If so, what would be the best way to accomodate that?

Best? A parent DC at each location with the child handling all DNS.

Most economical?
Secondary Parent zone on the Child DNS or forward to the parent from the
child. (But, NEVER from the parent to the child) Then, delegate the child
sub-zone in the parent zone to the Child DNS

This should about cover it all.
255248 - HOW TO Create a Child Domain in Active Directory and Delegate the
DNS Namespace to the Child Domain
http://support.microsoft.com/default.aspx?scid=kb;en-us;255248&FR=1