<p>I am debugging DNS using <a href="https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/" rel="nofollow noreferrer">dnsutils</a></p>
<p>I have created a dnsutils pod and I can see it running</p>
<pre><code>$ kubectl get pods dnsutils -n infrastructure
NAME       READY     STATUS    RESTARTS   AGE
dnsutils   1/1       Running   43         1d
</code></pre>
<p>When I run nslookup I am getting</p>
<pre><code>kubectl -n infrastructure exec -i -t dnsutils -- nslookup kubernetes.default


;; connection timed out; no servers could be reached

</code></pre>
<p>If I extract <code>/etc/resolv.conf</code> I can see</p>
<pre><code>kubectl -n infrastructure exec -ti dnsutils -- cat /etc/resolv.conf
nameserver 100.64.0.10
search infrastructure.svc.cluster.local svc.cluster.local cluster.local eu-west-1.compute.internal
options ndots:5
</code></pre>
<p>Any help how I can debug this further?</p>

Bob
<p>I have found out that I had some <code>calico-node</code> pods in <code>Running</code> state, but <code>1/2</code>, which I haven't noticed before. I had to kill these pods and also <code>calico-kube-controllers</code> several times, before they were recreated successfully. Then I killed <code>kube-dns</code> pods and everything is working now.</p>
