Can DNS Host records be artificial after Domain merge?
Posted on 2017-10-12
We are merging two domains into one. We have a library, .lib domain that will be going away, and server objects merging into parent domain. We want all the servers to maintain the .lib part of their name for application, web and certificate purposes.
We have the internal integrated AD DNS, and also an external DNS. I assume on Internal - when objects are moved between domains, the .lib server will be removed and the name will end in the only the primary domain. I assume I can make .lib type Alias records for these pointing to new name. For instance, abc.lib.contoso.edu will become abc.contoso.edu when switching domains - and I can Alias abc.lib.contoso.edu to abc.contonso.edu. Does that sound reasonable?
Then, on External DNS -- which is all manually can I just keep the abc.lib.contoso.edu with the same IP. The 'real' server will be abc.contoso.edu -- but the IP will be the same. Is there a need to setup a proper HOST record for abc.contoso.edu, then an Alias abc.lib.contoso.edu. Can I just leave things exactly as they are and not worry about DNS replication, etc.. Essentially, can I just leave abc.lib.conoso.edu HOST record - which is accurate now - the same after migration. It's IP will NAT to proper server - IPs are staying all the same. Will it matter that external HOST record is actually accurate as far as 'true' new server name? Then there's nothing to replicate.