We've just setup Hyper-V replica for most of our servers over to a DR site. First server I tried to bring up was our domain controller (FSMO master, 2012 R2.) We DO have other domain controllers, but wanted to make sure this solution also worked (As it should and has tested fine in other scenarios.)
We did a test failover, created a private NIC for the DC on the DR site's Hyper-V box, and booted the domain controller. Sat at the "please wait" forever, as if it's waiting for DNS. Once we get into the box, we're unable to open AD users and computers. Unable to do anything DC related. We adjusted the DNS on the NIC to only point to itself, rebooted again, and same results. All services are running. Can get into the DNS console and all looks good.
Opening AD users and computers gives us, "Naming information cannot be located because: The specified domain either does not exist or could not be contacted. Contact your system administrator to verify that your domain is properly configured and is currently online."
Nothing in the event logs jumps out at us - plenty of errors because it's looking for the other domain controllers. It does appear to be having an issue in that it can't contact DNS though, but not sure why as DNS is running and we see it fine. DNS server is listening on all IP addresses.
Appears the netlogon and sysvol shares are also gone.
Does this have something to do with the ability for server 2012 to properly virtualize and rollback DCs, and it won't advertise itself as a DC until it successfully ________?