I used the capabilities of Hyper-V 2012 to create a test environment that mirrors production systems (including a Domain Controller). I couldn’t get the other computers in the environment to use the replica for authentication. After a little more testing, I figured out that I couldn’t open AD DS on the DC.
Lots of searching on various errors eventually let me to this blog post, where a simple registry edit solved my problem:
Great to hear that you have resolved the issue using my article here: http://exchangeonline.in/windows-server-2012-naming-information-located-because-domain-exist-contacted/