Right, this is very complicated to explain. Please bear with me!
We are a split-site school. Currently there are 2 domains: upper school and lower school (one for each site). We going to migrate to one domain - phasing out the lower school domain.
The upper school has been upgraded to Server 2008. The lower school has a new 2008 domain controller which is set up with 'Sites' to replicate to the upper school.
The 'old' (currently in use) domain at the lower school is 2003.
Question 1 - how should DNS be set up on the lower school DC?
Currently, the contractor has set up a DNS server on the new lower school DC - OK. But, on the IP address setup on the server network card has configured the Primary DNS controller to be at the upper school, then the Secondary DNS controller to be at the lower school.
Surely, on a DC with DNS you should have it pointing to itself?
Is there a special way which the DNS forwarders/replication should be set?
On the lower site: We would like to setup and test Windows Deployment Services (WDS) on the new domain whilst leaving the old domain in place. WDS requires DHCP and DNS however, these are still hosted on the old domain. We also want to join and use computers on the new domain.
Can we continue to use the DHCP and DNS servers on the old domain? Will this complicate WDS?(Eventually, we'll move it over). Do we need to set up DNS fowarders or something to the upper school site?
Or block DHCP relay on the router(s) between the sites and set it up on each site, depending on your link speed. Getting an IP address may be ok, but actually booting windows PE and deploying an image over it may prove to be too slow.
Last edited by oxide54; 24th September 2009 at 02:03 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)