Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 567210 - sys-apps/busybox-1.23.1-r1 does not resolve DNS addresses
Summary: sys-apps/busybox-1.23.1-r1 does not resolve DNS addresses
Status: RESOLVED DUPLICATE of bug 509748
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Embedded Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-01 03:08 UTC by Ryan Twitchell
Modified: 2015-12-01 14:51 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info (emerge-info,5.36 KB, text/plain)
2015-12-01 03:08 UTC, Ryan Twitchell
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Twitchell 2015-12-01 03:08:23 UTC
Created attachment 418260 [details]
emerge --info

busybox-1.23.1-r1 appears to not perform any DNS resolution, for its functions that would normally do so (ping, wget, ntpd, etc).

Example of issue:

$ busybox ping google.com
ping: bad address 'google.com'
$ /bin/ping google.com
PING google.com (216.58.216.206) 56(84) bytes of data.
64 bytes from ord31s21-in-f206.1e100.net (216.58.216.206): icmp_seq=1 ttl=53 time=37.4 ms
64 bytes from ord31s21-in-f14.1e100.net (216.58.216.206): icmp_seq=2 ttl=53 time=38.3 ms
64 bytes from ord31s21-in-f206.1e100.net (216.58.216.206): icmp_seq=3 ttl=53 time=45.3 ms

tcpdump confirmed no DNS resolution performed.  nsswitch.conf is at its defaults, resolv.conf contains only google's DNS servers, resolution works fine except with busybox.

Appears to affect at least x86_64 and arm.

Uncertain how long this has been an issue as I have not used these utilities before.  Found a bug filed against Raspbian for busybox 1.22 with the same apparent symptoms:

https://bugs.launchpad.net/raspbian/+bug/1355063
Comment 1 SpanKY gentoo-dev 2015-12-01 14:51:12 UTC

*** This bug has been marked as a duplicate of bug 509748 ***