What is the appropriate coredns config using calico?

2/7/2021

None of the pods resolve public domains or any internal pods. The resolv.conf points to an ip that doesn't belong to coredns

IP of coredns: 192.168.208.7
#cat etc/resolv.conf
nameserver 10.96.0.10
search default.svc.cluster.local svc.cluster.local cluster.local ec2.internal
options ndots:5

What should i change to fix this dns issue?

-- Jeel
calico
coredns
kubernetes

1 Answer

2/8/2021

There are several steps you should take when Debugging DNS Resolution:

This page provides hints on diagnosing DNS problems.

Try in that order:

Sometimes it's just the matter of restarting the coredns deployment:

kubectl -n kube-system rollout restart deployment coredns

Also, there is always an option to install it fresh.

-- WytrzymaƂy Wiktor
Source: StackOverflow