Hoping someone can with this. We recently acquired another company and
they have a parent domain and a child domain. In the child domain DNS
resolves requests within itself and for external however not for the parent.
If we reference the parent domain it stops resolving requests for external
locations

MS Article 255248 on Child Domains references the following note but doesn't
give specifics for what the options would be for or why they may be needed

Optional Configuration Considerations
NOTE: The following options depend on how your organization wants to setup
its DNS name resolution and namespace, and using proxy servers or firewalls
can influence this decision as well. • On the TCP/IP properties of the child
domain server, change the TCP/IP address of the DNS server to point to its
own TCP/IP address.
• Consider integrating DNS with the Active Directory on the child DNS server.
• Add the parent (root) DNS server as a forwarder on the child DNS server.

"PRSmith59" <PRSmith59@discussions.microsoft.com> wrote in message
news:B7F6375B-3F65-410A-8881-C8220E122435@microsoft.com...
> Hoping someone can with this. We recently acquired another company
> and
> they have a parent domain and a child domain. In the child domain DNS
> resolves requests within itself and for external however not for the
> parent.
> If we reference the parent domain it stops resolving requests for external
> locations

Parent domains should (generally) DELEGATE to child domains.

Child domains (Win2003) should generally "conditionally forward"
to parent domains if they live in a (semi-)private DNS area as most
do. In Win2000 they may have to keep a 'secondary' for the parent
since conditional forwarding is not available, and in Win2003 there
are actually a bunch of choices besides Conditional Forwarding.

> MS Article 255248 on Child Domains references the following note but
> doesn't
> give specifics for what the options would be for or why they may be needed
>
> Optional Configuration Considerations
> NOTE: The following options depend on how your organization wants to setup
> its DNS name resolution and namespace, and using proxy servers or
> firewalls
> can influence this decision as well. . On the TCP/IP properties of the
> child
> domain server, change the TCP/IP address of the DNS server to point to its
> own TCP/IP address.
> . Consider integrating DNS with the Active Directory on the child DNS
> server.
> . Add the parent (root) DNS server as a forwarder on the child DNS server.

This is possible but not really a "generally solution".

Also make sure you have NO MUTUAL (and unconditional) FORWARDING.
(DNS-Parent must not forward to child with DNS-child forwarding to parent.)

--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]