On 25 October 2014 23:30, <[email protected]> wrote: >> >> $ /usr/local/bin/busybox nslookup example.com >> Server: (null) >> Address 1: (null) >> Address 2: 127.0.0.1 localhost.localdomain >> >> Name: example.com >> Address 1: (null) >> Address 2: 93.184.216.119 > > okay, it's not just bionic but musl too. > > the musl resolution looks particularly evil with address1 being null. > I didn't dare to suggest this before but if musl was trying to resolve > the IPv6 address there to null then maybe this bug is related to > ENABLE_FEATURE_IPV6
Hmm, maybe the opposite? $ /usr/local/bin/busybox bbconfig | grep IPV6 # CONFIG_FEATURE_IPV6 is not set # CONFIG_FEATURE_IFUPDOWN_IPV6 is not set $ /usr/bin/busybox bbconfig | grep IPV6 CONFIG_FEATURE_IPV6=y CONFIG_FEATURE_IFUPDOWN_IPV6=y <change config and recompile musl version> $ ./busybox-ipv6 nslookup example.com Server: (null) Address 1: ::1 Address 2: 127.0.0.1 localhost.localdomain Name: example.com Address 1: 2606:2800:220:6d:26bf:1447:1097:aa7 Address 2: 93.184.216.119 Doh! You were right about the null being ipv6 - but I don't think this makes things any better :( Thanks, Steven _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
