https://rancher.com/ logo
Title
n

nice-pager-21194

05/07/2023, 4:12 PM
Hi all My DNS is not working from pods running on worker nodes, getting ";; connection timed out; no servers could be reached" error. I have tested by ssh to pods running on worker and tried "nslookup google.com 10.43.0.10" command where 10.43.0.10 is ip of my kube-dns service. "nslookup google.com 10.43.0.10" command is not working from worker node directly either, where as only ""nslookup google.com" is working fine on worker node "nslookup google.com 10.43.0.10" command is working on pods running on Master node as well as from master node too. Please check the attached screenshot. Everything was working and tested on the same cluster earlier but started failing suddenly recently, and now it is not working on pods on worker nodes as well as from worker nodes Please help!
r

rough-farmer-49135

05/08/2023, 5:00 PM
Your worker & master nodes won't be able to access the 10.42 or 10.43 networks. Those are set non-routeable from the host OS. You'll need to create a shell in a running pod if you want to test DNS. If you're running Rancher it's an easy option, if not it can be done with a
kubectl exec
command (though I always botch it at first and have to look up the right syntax to run bash).