Are you referring to ZOC nodes using IPv6 addresses? Yeah, it's a bit of a tricky situation and I'm afraid I don't have clear advice to give you. I can tell you what's happening with IPv6 nodes, though. As you've probably noticed, they have limited connectivity relative to their IPv4 brothers because most of the network is IPv4, and most IPv6 nodes are single-stack and therefore don't talk to the IPv4 side. In the past, this is what was causing our chainsplits, hence the need to introduce self-healing chain rules in v0.12.3.7. From a masternode perspective, this can lead to the network being more likely to label IPv6 nodes as "unhealthy" (due to having more consensus disagreements) and thus they earn reduced rewards compared to healthy nodes. That's actually being done on purpose to preserve the health of the masternode network.
So what's the takeaway here? That I don't really know. The easy answer is use IPv4. But I know that's not always feasible. cmelx says that if you use 'externalip=' instead of 'bind=' in your conf, though, then an IPv6 node should still be able to communicate with other IPv4 nodes provided your VPS has an IPv4 address as well. I can't personally vouch for that because I haven't tested that scenario myself.
Sadly, everything "sort of runs" but doesn't when 'bind=' is removed... will masternode something else for a while, rolling back to a prior version would obviously be counter productive for the network. Have you resolved the long waits in block movements? The latest wallet is very good compared to the last wallet. If Cmelx wasn't so sensitive, i'd give him a compliment.
