busybox 1.29.3 misbehaving when doing nslookup to public URLs
shiveshabhishek opened this issue · comments
Shivesh Abhishek commented
I've seen this strange issue while working with busybox v1.29.3 in Rancher k8s cluster v1.23.13+rke2r1
. It's unable to do nslookup
shivesh@shivesh-machine:~/rancher$ kubectl run -i --tty --rm debug --image=busybox:1.29.3 --restart=Never -- sh
If you don't see a command prompt, try pressing enter.
/ # nslookup github.com
Server: 10.43.0.10
Address: 10.43.0.10:53
Non-authoritative answer:
*** Can't find github.com: No answer
But when I'm trying to do the same from pod with the latest busybox image, it worked flawlessly.
shivesh@shivesh-machine:~/rancher$ kubectl run -i --tty --rm debug --image=busybox --restart=Never -- sh
If you don't see a command prompt, try pressing enter.
/ #
/ # nslookup google.com
Server: 10.43.0.10
Address: 10.43.0.10:53
Non-authoritative answer:
Name: google.com
Address: 2404:6800:4007:818::200e
Non-authoritative answer:
Name: google.com
Address: 142.250.77.174
/ # nslookup github.com
Server: 10.43.0.10
Address: 10.43.0.10:53
Non-authoritative answer:
Non-authoritative answer:
Name: github.com
Address: 20.207.73.82
/ #