Single Windows DNS Server with multiple V-Lans
Posted on 2010-11-17
We are getting some outside CCNA/CCNP guys to help us segment our single V-Lan network. They want to setup our old Cisco 2600 Router to give us several v-lans. We want to future proof the network as much as possible for growth of each department. We aren't too knowledgeable about this process but are working hard to learn as much as we can so that we can manage it well when the help is gone. They are enabling inter-V-Lan Routing so each segment can talk to each other. They want to let the Cisco router handle DHCP and they aren't sure about internal DNS.
Our first question is: How does internal DNS work with V-Lans and Inter-V-Lan Routing? The CCNA guys said they would have the Cisco router manage DHCP, but us Microsoft guys cringed at that. We are not looking forward to learning how to run the Cisco router well enough to troubleshoot IP Address problems if they arise in the future after the help leaves. Our thought is to set it up so windows servers handle both DNS and DHCP. Can a single Windows server handle this? Will there need to be a DNS and DHCP server for each V-Lan? We are considering approximately 8-9 V-Lans so that may be too many windows servers.
If we use one Server for DNS and/or DHCP would there have to be a different NIC for each V-Lan?
We are open to any ideas that would allow us to manage our network easily as time goes on. We aren't opposed to learning the Cisco stuff, but it isn't a quick process and time is of the essence in this situation.
Thanks for any thoughts you can add!