AWS EKS Cluster DNS Pod Issue

coredns

#1

I have a running AWS EKS cluster with 2 worker nodes of type T2 and M3. I have mongo deployed on M3 and my application code deployed on T2. If kube-dns pod is running on M3, then microservices don’t talk to mongo, but if it runs on T2, microservices can talk to mongo. How to work on this problem?