<p>None of the pods resolve public domains or any internal pods. The resolv.conf points to an ip that doesn't belong to coredns</p>
<pre><code>IP of coredns: 192.168.208.7
</code></pre>
<pre><code>#cat etc/resolv.conf
nameserver 10.96.0.10
search default.svc.cluster.local svc.cluster.local cluster.local ec2.internal
options ndots:5
</code></pre>
<p>What should i change to fix this dns issue?</p>

Jeel
<p>There are several steps you should take when <a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/" rel="nofollow noreferrer">Debugging DNS Resolution</a>:</p>
<blockquote>
<p>This page provides hints on diagnosing DNS problems.</p>
</blockquote>
<p>Try in that order:</p>
<ul>
<li><p><a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#check-the-local-dns-configuration-first" rel="nofollow noreferrer">Check the local DNS configuration</a></p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#check-if-the-dns-pod-is-running" rel="nofollow noreferrer">Check if the DNS pod is running</a></p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#check-for-errors-in-the-dns-pod" rel="nofollow noreferrer">Check for errors in the DNS pod</a></p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#is-dns-service-up" rel="nofollow noreferrer">Check if DNS service is up</a></p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#are-dns-endpoints-exposed" rel="nofollow noreferrer">Are DNS endpoints exposed?</a></p>
</li>
<li><p><a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#are-dns-queries-being-received-processed" rel="nofollow noreferrer">Are DNS queries being received/processed?</a></p>
</li>
<li><p>and the <a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#known-issues" rel="nofollow noreferrer">Known issues</a></p>
</li>
</ul>
<p>Sometimes it's just the matter of restarting the coredns deployment:</p>
<pre><code>kubectl -n kube-system rollout restart deployment coredns
</code></pre>
<p>Also, there is always an option to <a href="https://kubernetes.io/docs/tasks/administer-cluster/coredns/" rel="nofollow noreferrer">install</a> it fresh.</p>
