AD and Sub-Domains (Forest Tree question)

[Corneliu]

I have a main windows 2003 server (the main top headquarters server). What I want to do is to add another server under that tree from a different location. This is what I mean:

Headquarters Server
Windows 2003, DHCP, DNS, IIS, AD

Computer Name: Main-Corp
Domain: Maincorp
IP: 192.168.0.2
DNS: 192.168.0.2
Tree: Corp.com

Now, I want to add another server from a differnt location to the MAIN Active Directory (maincorp).

Florida Server
Windows 2003, DHCP, DNS, AD

Computer Name: Florida-Corp
Domain: FloridaCorp
IP:192.168.0.3
DNS: 192.168.0.3
Tree: Florida.corp.com

I setup the main server (headquarters) and ran dcpromo and activated the AD, and setup all that stuff.

Now, when I setup a second server (same LAN for now, then will be moved later), I try to run DCPROMO and add it as Second Domain in existing forest. But it does not work, It comes back with:
Cannot find the maincorp domain. Please check your DNS and try again.

What am I doing wrong? Or is this correct?
Do I have the schema right or is it supposed to be different?

There will be many remote location servers and one main server (this is what I think would be the best setup). All the servers will be Windows 2003 OS. After readin some help files and support from microsoft's web site and some books, it should this would be an ideal network.

What am I doing wrong? Do I have to forward DNS entries or something like that?


Thank You very Much...

 

[mlichstein]

Make sure the florida server is pointing to the HQ server for DNS.

Also, did you mean to type maincorp.com in dcpromo or just corp.com?

 

[Corneliu]

I meant corp.com, sorry for the confusion.

When you say point the Florida Server to HQ server in DNS, you mean create the forwarders, or what you mean by that?

If I have to create the forwarders to the HQ server, how I do that one? I know you do it in DNS Manager, but I never done that before (a bit new to 2K servers), but how exactly?


Thank You for your help...

 

[mlichstein]

No, I mean configure the primary DNS server on the Florida server with the IP address of the HQ server.

 

[Corneliu]

If I configure the Primary DNS Florida server with the HQ Server IP, wont that be really slow? (over say a VPN).

Currently it is on a LAN, but soon will be moved and connected via VPN. Will that be slow?

And if its now, then will the users from the florida location use the DNS server Florida or HQ DNS Server?

Thank you

 

[mlichstein]

Ok, you could configure a forwarder. You should have already delegated down, now you need to forward up.

Right click on the server object in Florida's DNS console and go to the forwarders tab. Add the IP address of the HQ server. You still need to go over the VPN at some point to resolve the other domain, regardless of if you use a forwarder or point directly to the server.

The Florida clients should point to the Florida server.