Multiple Subnets, Single Server 1

[kopar]

All right. I'll try and explain this as succinctly as I possibly can.

Our organization has reached a point of reorganization and we are exploring options for our internal network structure. We currently have three subnets (10.2.x.x, 10.3.x.x, 10.4.x.x). Each one is running it's own DNS and DHCP servers without any primary DNS controller.

10.2 is primarily a windows 2k XP network, with a 2K server running DHCP/DNS.

10.3 is primarily a Linux environment with a RedHat DNS/DHCP system in place.

10.4 is running Linux, Windows and Solaris systems, running a modified DHCP/DNS system on RedHat.

Our current setup does not allow for DNS resolution between the three networks, but does allow for IP communication. We would like to consolidate the DNS/DHCP services to a single machine, begin using Active Directory and ensure interoperability between the subnets. Is this possible using Windows 2K Server?

I'd also like to entertain opinions on other alternatives if you have them.

Thanks!

 

[kmcferrin]

I'm not sure why you have multiple DNS/DHCP servers unless the networks are separated by a WAN or other slow link. You can just as easily create a single Windows 2000 server with AD, DNS, and DHCP.

For DHCP define a separate scope for each of your three subnets, and make sure that your routers are forwarding DHCP requests between the networks. Win2K DHCP will see which subnet the request came from and assign an appropriate IP address. We have 15 or 16 different subnets on our network that are server by a single DHCP server and a pair of DNS servers.

As far as DNS goes, there's no requirement to have a separate DNS server for each platform or subnet. All of my subnets are serviced by a pair of Win2K DNS servers (the second is for redundancy only). If you are dynamically registering DNS records in DHCP then your Linux/Solaris machines should still get their NetBIOS names registered in DNS with the leased IP. The only real issue that you need to watch for is making sure that you manually add DNS records for the Linux/Solaris *servers* who have static IP addresses. The Windows servers should be taken care if they are members of the AD structure (DNS being the backbone of AD, as it is).

 

[kopar]

First off, thanks a bunch.

I think we have several DNS servers for several reasons. The primary one being a lack of knowledge when the network was being created. The second is the need for specialized equipment in one portion of the organization (they will continue to use thier own DHCP server).

Can you suggest a good switch/router that offers DHCP forwarding for use in this situation. (Or specifics on what we should look for when shopping?)

 

[GrnEyedLdy]

Kopar,

Any router that is RFC 1542 compliant will allow forwarding of DHCP discover packets. Alternately you could always install DHCP Relay Agents on each subnet which will speak to the DHCP server on your clients behalf. Installing a Relay Agent is simple and done through the RRAS console.


Patty

 

[kopar]

I guess I should be more specific. I would like to know if there are any standout managed switches/routers that will allow me to do the following:

1) Create multiple network segments (10.2.x.x, 10.3,x,x, etc.)
2) Do DHCP unicast forwarding
3) Allow each segment to communicate (10.2.x.x can talk to 10.3.x.x efficiently)

Also opinions about CLI interface preferences are certainly welcome.

Thanks in Advance!

-Tom

 

[kmcferrin]

I'm not the best when it comes to actual networking hardware, but pretty much any modern router should allow this (and most managed switches). As you know doubt are aware, Cisco is pretty much the industry leader.