2 Domains on 1 LAN?

[john.gardner]

I would like to build a replacement domain in the school i work at but i only have 1 LAN, can i simply exclude some DHCP address from the current domain and place the new domain on the pinched IP addresses to build and test the new domain? i cant see how DHCP would work as when a client plugged into the LAN it would see 2 conflicing DC's, DHCP server DNS etc. (i have tryed to get an extra LAN from SWGFL but they are taking forever to get back to me)

[OutToLunch]

You'll be wanting static IP's on one domain using the reserved portion and DHCP on the other, unless you're using MAC addresses to exclude/allocate reserve DHCP IP's I think... We're running two here on the same physical LAN but using totally different IP ranges for the admin machines rather than carving them off the DHCP.

e.g 192.168.0.x for curric, 192.168.16.x for admin.

[john.gardner]

OK thanks, I have excluded a 254 IP range from the existing DHCP leases and would have liked to have DHCP on the new domain is this 'doable', and could i now create this new domain DNS, DHCP, on the LAN or would i need to do anything else to stop service conflictions?

[antoeknee]

Like OutToLunch I run two domains with totally different IP ranges.

One is setup with static IP which we use for the admin domain and the other use DHCP for the curriculum domain.

Admin is 172.16.x.x and curric 10.10.x.x

Just to be safe I've setup a one way trust so that its possible to get to curric from the admin but not the other way round.

[chaz6]

Until the old domain is deprecated, we run two domains side-by-side on all the access networks (i.e. building vlans). All clients use the same dns and dhcp servers (ISC dhcpd and ISC named as opposed to Windows DHCP/DNS). This /would/ be a problem if ever you wanted to use RIS/WDS on both domains as you would then need to separate your clients (or do lots of horrible static configuration).