[Bug 13006] nslookup problems

bugzilla at busybox.net bugzilla at busybox.net
Wed Dec 30 13:52:01 UTC 2020


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

--- Comment #3 from Denys Vlasenko <vda.linux at googlemail.com> ---
(In reply to evans.tucker from comment #1)
> I see this problem in the uclibc version

uclibc has a rather primitive support for resolver routines, thus nslookup on
uclibc is likely to be buggy: nslookup just overrides default DNS address, then
uses standard name resolution in libc to get addresses.

Even such trivial thing as setting DNS server address to a IPv6 address does
not work.

LEDE project contributed a better version of nslookup, it is enabled by setting
FEATURE_NSLOOKUP_BIG=y but it requires a libc with a decent resolver support:
uses ns_initparse(), ns_msg_count(), ns_parserr() etc. It will not compile on
uclibc (did not try uclibc-ng).

So. What version of busybox is it?
Is FEATURE_NSLOOKUP_BIG=y ?

> 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

What is the exact problem in the above? It said that AAAA request was replied
with no records ("No answer") and A request was successfully answered with an
IP address.

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


More information about the busybox-cvs mailing list