Ah, I see, you are referring to a lab found on the GNS3Valut site. Thanks for clearing that up.
The multicast routing process that deals with routing multicast traffic is something that is independent of the multicast addresses used by routing protocols to share their data. Yes, within the multicast routing domain, 220.127.116.11/24 is not routed, but EIGRP is still able to exchange its routes using that address. EIGRP functions just fine in a multicast environment.
You simply have to ensure that your multicast addresses used in your topology are not in the 18.104.22.168/24 subnet, as these are reserved and actually, cannot be routed.
As mentioned in the previous post, these are unroutable by design, and will always be dropped by the multicast routing process, as described in RFC 5771. Using dense mode or ip mroute will not change this.
I hope this has been helpful!