<p>I have Kuberenets cluster with AWS-EKS, Suddenly on my cluster existing pods were unable to resolve DNS host name when i try to check NSLookup internally in pods.
Can someone please suggest me like
1. How to resolve this DNS resolution among pods 
2. What change causes my cluster to go like this all of sudden</p>

Lakshmi Reddy
<p>Chek youre namespaces.
The kube-dns works in the following way:</p>

<p>get pod in the same namespace: curl <a href="http://servicename" rel="nofollow noreferrer">http://servicename</a></p>

<p>get pod in a different namespace: curl <a href="http://servicename.namespace" rel="nofollow noreferrer">http://servicename.namespace</a></p>

<p><a href="https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/" rel="nofollow noreferrer">Here</a> and <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/" rel="nofollow noreferrer">here</a>
Understanding namespaces and DNS
When you create a Service, it creates a corresponding DNS entry. This entry is of the form ..svc.cluster.local, which means that if a container just uses  it will resolve to the service which is local to a namespace. This is useful for using the same configuration across multiple namespaces such as Development, Staging and Production. If you want to reach across namespaces, you need to use the fully qualified domain name (FQDN).</p>
