Re: Global catalog issue

Tech-Archive recommends: Fix windows errors by optimizing your registry

In news:1131754476.592339.14510@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
louey-3@xxxxxxxxxx <louey-3@xxxxxxxxxx> made this post, which I then
commented about below:
> you mean I must run DNS on the child domains.............. rather than
> just the forest level DCs.

What Brian is saying is the child domains must be able to resolve the forest
root _msdcs zone, no matter how it is configured, whether (1) ALL machines
are only using the forest root domain's DNS, (2) you have delegated the
child zone from the parent to the child and set a forwarder back to the
parent, and since the servers are Win2003, you want to make sure the _msdcs
zone is available on the child, or (3) using a Stub zone.

Whatever way, you must insure full DNS resolution of all domains in an
infrastructure or not telling what will happen.

If you are saying DNS only is installed at the root, then may I assume that
all of the child domain DCs and clients are ONLY using the DNS server(s) in
the root domain ONLY?

I'm implying that you have no other DNS servers configured in the child
domain's machines' IP properties (such as an ISP's DNS or some other
external DNS that doesn't host your AD zone, etc), otherwise, I can
understand why you are getting the errors.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================


.

Relevant Pages

  • Re: Event ID 7062 in DNS logs
    ... you advice me to let the default Internet root ... > hints in place and to use forwarders from the child DNS (DNS server in ... > the root DNS (DNS server on the forest root domain hosting the ... > AD-integrated forestroot.com zone). ...
    (microsoft.public.windows.server.dns)
  • Re: DNS
    ... DNS was pointing to the the DC at Site A which already had a AD ... DNS zone replicating from the DNS server in site A and everything was ... Assuming you created a child zone at B, apparently the zone for B is a child zone under A. Assuming zone A's default replication scope is still set to "All DNS Servers in teh Domain," B's servers will never see the zone becaues they aer in a different domain. ... You would also need to create a forwarder from your DNS servers to the parent zone's DNS servers, which we will assume are Forwarded out to the ISP. ...
    (microsoft.public.windows.server.dns)
  • Re: set up first child DC in a remote site
    ... has not set its IP and DNS in the creation of ... delegation can the parent DC see the child DC-to-be? ... and child zone created as the Conditional forwarding configured pointing to ...
    (microsoft.public.windows.server.active_directory)
  • Re: Misconfigured AD
    ... Currently the Child Domain DC is configured as a secondary DNS ... The Parent DC is also the Primary DNS Server. ... ROOT created as a zone on your DNS server, or is that that actual Root ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 DNS Setup for Sub-Domain off of Root
    ... > dns in any other zone than the one that is assigned to them. ... > delegating each sub-domains zone from the root domain. ... they are not needed on the root domain DNS servers as the actual ... > the root zone from the sub-domains dns server. ...
    (microsoft.public.windows.server.dns)