- We have DR site that needs to be tested
There is a mix of Linux and Windows hosts on DR site.In case of disaster if SERVER in production site is not available, SERVER_DR on DR is switched on and joined to the same Windows domain.This is done this way in case primary site is not available and we don't want to delete original record for SERVER form AD.
The problem I am trying to solve is a name resolution in DR site.Processes and scripts are using DNS name SERVER so in DR site requests to SERVER should translate to SERVER_DR. We have no access to do anything on Windows DNS.
My idea is to use BIND to solve this problem.Hosts in DR should be able to authenticate with AD .Fact that they don't need to access anything else outside the DR site in Windows domain should simplify the problem.
Services that need to be accessed by DR hosts are mostly file sharing and SQL servers.I believe SQL servrers maybe a problem here since they use SPN
This brings an idea of using BIND for our.domain.com zone held by BIND in DR site, however I can see possible problem when Windows DR hosts need to authenticate against AD since they need to use undescored records if I remember correctly.We cannot delegate zones from AD due to the reasons I mentioned earlier.
Is it worth trouble to solve this problem?One of my colleagues suggested using hosts file for each Windows DR host.However it seems pretty ugly there are not many of them and my time setting up BIND may be wasted.