ping: bad address, Running in k8s.

root@linuxserver-image-0:/# cat /etc/resolv.conf
search somewhere.svc.cluster.local svc.cluster.local cluster.local local.mydomain.com
nameserver 10.152.183.10
options ndots:5

root@linuxserver-image-0:/# nslookup google.com
Server:         10.152.183.10
Address:        10.152.183.10:53

Non-authoritative answer:
Name:   google.com
Address: [multiple results omitted. works fine.]

Non-authoritative answer:
Name:   google.com
Address: [multiple results omitted. works fine.]

root@linuxserver-image-0:/# ping google.com
ping: bad address 'google.com'

Modifying /etc/resolv.conf, changing ndots:1, to ndots:1, makes everything work somewhat normally.

root@linuxserver-image-0:/# vi /etc/resolv.conf
root@linuxserver-image-0:/# ping google.com
PING google.com (74.125.198.100): 56 data bytes
64 bytes from 74.125.198.100: seq=0 ttl=104 time=26.945 ms
^C
--- google.com ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 26.945/26.945/26.945 ms

There are tons of somewhat related tickets on this one, most, however, have the opposite issue where nslookup doesn't work, but, ping does work.

There are tons of upstream tickets in say, linuxserver.io repos, referencing these closed tickets.

However, there isn't a published work-around for this issue, nor, is there much of a paper-trail as to where/who/when this issue will be resolved.

Start by reproducing the BusyBox container behavior on Kubernetes with the shown /etc/resolv.conf, comparing ping and nslookup at ndots:5 and ndots:1. Review the related upstream tickets referenced in the report and trace where the resolver behavior differs; done means the cause and a documented workaround or fix are established.