Installing the Hyper-V role on a domain controller is likely to cause issues. Multi-homing will always cause no end to grief to active directory domain services. Adding the Hyper-V role likely added additional network connections, possibly changing the route, and the network firewall profile in use which would also affect allowed ports.
I'd suggest installing the Hyper-V role as only role on host, then stand up virtual machines for the various roles and or applications.
--please don't forget to Accept as answer if the reply is helpful--