General discussion


DHCP with 2 Servers and 2 Networks

By Uncle Marv ·
I'm looking for help or documentation for setting up the following. We have a client that wants...

1) Two servers hosting seperate domains
2) Each domain on a separate subnet
3) Adding third subnet within year
4) Both networks able to see/ping each other
5) Possibility of each server as DHCP?

I've looked at having a subnet of which means we could use -

Any help would be appreciated.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by curlergirl In reply to DHCP with 2 Servers and 2 ...

First, set up your separate domains. Each domain will need its own DHCP and DNS servers, DC's, etc., for its subnet.

If you want the users in both domains to be able to use resources in both domains, you need to either configure them as subdomains of the same forest, or create a permanent trust relationship between the two domains. How you do this depends on how interdependent you want these domains ultimately to be. If you create two separate forests/domains with a trust relationship, it's very easy to break them apart. If you create one forest with two subdomains, it can be complicated to then split them apart if you need to.

Set up two routers, one for each subnet, to route between the two subnets. If you're using two separate Internet connections, you would set them up separately on the two routers. This makes the routing a bit more complicated, as you have to set up a static route from subnet A to subnet B. If you are using only one Internet connection, you can simply route from one of the routers through the other one to the Internet.

I would recommend having a DHCP server in each subnet rather than trying to configure one DHCP server to handle everything. DHCP packets will not be forwarded by the router unless you specifically configure it that way (if the router has that capability) or set up one of your servers in the non-DHCP subnet to be a DHCP proxy.

As far as the actual IP address range for each subnet, I would be more inclined personally to stay as simple as possible:

Subnet A: -, default mask of

Subnet B: -, default mask of

When you add another subnet, just keep going with -; etc.

(cont'd in comment)

Collapse -

by curlergirl In reply to

Unless you will have more than 200 or so workstations in each subnet, that should do you fine. Since you're using private IP addressing, there's really little reason to make it any more complicated than that, IMO. Maybe someone else will have another point of view to offer.

Hope this helps!

Related Discussions

Related Forums