VLANs, DNS, VMWare

Hi all, I need some help with VLANs, DNS, VMWare and the equivalent in HyperV. I have just been put in charge or a network with what seems to me a very strange (or could be just wrong setup).
The setup:
I have 3 servers in a VMware cluster. 5 NICs in each node. 1 NIC for every node is connected to physically separate storage network (2 x SANs) and the other 4 NICs (per node) are teamed to a LACP trunk with 10 VLANs (all normal so far). In VMware a Virtual NIC for each VLAN has been created. We have 3 x servers running AD & DNS (one is physical and just connected to VLAN2). The 2 virtual AD / DNS servers have 5 virtual NICs each connected to them, each virtual NIC on a different VLAN. Only 1 reverse lookup is set in DNS and that only covers 1 of the VLANs. The 2 virtual AD /DNS servers are showing a lot of 7005 DNS errors, seem to try and reply to pings using a IP not in the subnet of the machine pinging it and when connecting to the DNS via an RSAT machine you have to connect to the IP as connecting to the name often resolves the wrong IP (for the RSAT machines VLAN) and then of course errors and fails to connect. I can’t see the reason or logic behind a setup like this and took it as an unwritten rule that you should never multi-home a DC
Question 1: Am I missing something or not understanding something?
Question 2: I may not be able to wrap my head around this setup but I am pretty sure it’s the main reason why I get some very strange errors reported and network performance is excuse the un-techie term but rubbish
Question 3: What is the best way to deal with multiple VLANs in a VMWare configuration like this / is there a simple fix?
Question 4: This and other issues I am finding is making me think my best long term solution is to start a new network hosted on HyperV (as I personally find it much easier to work with) and plan a big rework of the whole network. Any advice or different advice on the same setup with HyperV