DNS, Active Directory, and WAN configuration 1

[igolo]

I need help determining the most efficient use of these three technologies.
At the HQ I have the parent domain corp.work.com (server 2003, AD, & DNS) and I have about 100 national sites (only about 20 server 2003 so far) connected via broadband WAN. Each remote site has or will have an AD server with DNS in the form of remote1.corp.work.com.
The problem:
Recently I've been noticing a problem, with new remote servers, where the clients in the remote domain could resolve names locally, but were not able to resolve back to the HQ.
ex. RemClnt1 could resolve RemClnt2, but could not resolve HQfilesrv

I verified that the routers were passing dns. the dns entries at the remote server point HQ DNS servers and RM clients point to their local server for dns.

The question:
How do I get my remote servers to forward HQ DNS request from the client? More importantly can this be setup during the install process?

 

[ShackDaddy]

Tell me if I'm wrong, but it sounds like you might have built something that LOOKS like a proper DNS tree, but isn't since they only use hierarchical names but not an actual cohesive hierarchical infrastructure. Are the remote sites really subdomains in the same tree, or were they set up without reference to the existing AD? If done right, your remote DNS servers should be able to refer queries back to HQ.

But you haven't actually given us much information about your actual AD/DNS implementation, so this is all guessing, and probably not giving you enough credit. Would you like to share more about how you built your tree out?

ShackDaddy

 

[basst]

You need to ensure that the remote DNS servers have the HQ DNS servers as forwarders.

Alternateively you could host secondary zones of the HQ zone on the remote servers.

 

[igolo]

Yes, the remote sites are subdomains of in the same tree.
basst, adding the forwarders worked.