[Bug 13006] Nsloockups problems

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=13006

--- Comment #1 from evans.tucker at gmail.com ---
I see this problem in the uclibc version:

```
$ kubectl run -it --rm evanstest-b5 --image=busybox:1.32.0-uclibc -- sh
If you don't see a command prompt, try pressing enter.
/ # nslookup opentelemetry-collector.observability.svc.cluster.local
Server:         10.0.0.10
Address:        10.0.0.10:53

*** Can't find opentelemetry-collector.observability.svc.cluster.local: No
answer

*** Can't find opentelemetry-collector.observability.svc.cluster.local: No
answer

/ # 
```

The musl and glibc versions partially work:

```
$ kubectl run -it --rm evanstest-b3 --image=busybox:1.32.0-musl -- sh
If you don't see a command prompt, try pressing enter.
/ # nslookup opentelemetry-collector.observability.svc.cluster.local
Server:         10.0.0.10
Address:        10.0.0.10:53

*** Can't find opentelemetry-collector.observability.svc.cluster.local: No
answer

Name:   opentelemetry-collector.observability.svc.cluster.local
Address: 10.0.228.84

/ # 

$ kubectl run -it --rm evanstest-b4 --image=busybox:1.32.0-glibc -- sh
If you don't see a command prompt, try pressing enter.
/ # nslookup opentelemetry-collector.observability.svc.cluster.local
Server:         10.0.0.10
Address:        10.0.0.10:53

Name:   opentelemetry-collector.observability.svc.cluster.local
Address: 10.0.228.84

*** Can't find opentelemetry-collector.observability.svc.cluster.local: No
answer

/ #
```

The Kubernetes community has been working around this issue for a couple of
years by pinning to busybox:1.28 - what can we do to help fix this issue?

-- 
You are receiving this mail because:
You are on the CC list for the bug.