I have a DNS Standalone Server installed on an old 2K3 Windows Server to migrate to a 2008 Active Directory. All hosts are an old Workgroup architecture...
I have now two fully functional 2008 R2 available on the local network, both integrated to the enterprise AD domain, with 98% of the hosts on the network resolved by them. But some hosts are on heavy industrial needs and have high availability requirements and could not been migrated to the new DNS 2008 R2 server for now.
To get access to the Enterprise Proxy and been integrated within the current DNS global infrastructure, the previous team did "copy/paste" two internal DNS “zones” on the standalone server and redirected their requests to the INET side ".org" Linux DNS servers (Its current redirectors).
In order to now, retrieve theses direct requests to the INET zone, and now proceed with the "normal" DNS hosts resolution, I need to change the old DNS server redirectors from the Linux INET Servers to the 2008 AD/DNS ones...
Referring to the attached figure of the current migration process we have, my question is:
What should now be at your point of view, the better way to avoid the Old Standalone DNS Server to have the linux Inet DNS server as redirector and configure its current requests to the Active Directory Migrated DNS servers?
Thanks all for your advices!
Thanks for posting here.
According to your situation, you can setup conditional forwarders to forward queries to the migrated DNS server based on the DNS domain names that are in the queries. If you want to forward any queries that the old standalone DNS server cannot resolved, we need to configure the forwarders on this DNS server. For detailed information about Forwarders, please refer to the following articles:
Conditional Forwarding in Windows Server 2003
Configure a DNS Server to use Forwarders
TechNet Community Support
Thanks for your answer ! Appreciated ! :)
We were thinking the same type of solution for our Architecture Change on this project.
But the question is that, before setting up a any simulation of the whole infra, we did think that another point of view could make the difference.
The real question is not where should be configure the forwaders which is quite clear, but how to keep the old infra "as it is" during the "after migration phase" when we still have "something" ; "somewhere" refering to the old infra... ;)
For exemple Deleting "all" the configured zones on the OLD DNS server, and forward to the new infra... But we may still forgot something... ;)
This is one view there are maybe others...
Do not hesitate to share about your point... We are maybe totaly wrong... ;)
Thanks again for participating. :)
- Edited by BertrandTHOMAS Thursday, February 23, 2012 9:59 AM Update