flat-translator-3220411/17/2022, 4:51 PM
however upon logging onto that pod and trying to ping 126.96.36.199, the packets are being transmitted successfully.
wget: unable to resolve host address
Note: 1. Security groups are proper with access to all http traffic. So I am not sure why the DNS resolution is failing on the EC2 instances. I have tried restarting coredns service
bash-4.3# ping <http://google.com|google.com> ping: bad address '<http://google.com|google.com>' bash-4.3# ping 188.8.131.52 PING 184.108.40.206 (220.127.116.11): 56 data bytes 64 bytes from 18.104.22.168: seq=0 ttl=49 time=1.133 ms 64 bytes from 22.214.171.124: seq=1 ttl=49 time=1.084 ms --- 126.96.36.199 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.083/1.109/1.137 ms bash-4.3#
and it temporarily fixes the issue but when I delete and recreate the pod, I again see issue with DNS resolution. Please let me know of there is anything needs to be changed in config files or is there any setup issue.
sudo kubectl -n kube-system rollout restart deployment coredns