[Bug network/20626] New: Unable to resolve host name on MIPS (MIPS-II, o32)

["jeffbai at aosc dot xyz" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=20626

            Bug ID: 20626
           Summary: Unable to resolve host name on MIPS (MIPS-II, o32)
           Product: glibc
           Version: 2.24
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: network
          Assignee: unassigned at sourceware dot org
          Reporter: jeffbai at aosc dot xyz
  Target Milestone: ---

After updating to Glibc 2.24, some programs, for example, wget, curl, and apt
are no longer able to resolve a host name. As shown follows:

root [ autobuild3@master ] # apt update
Err:1 https://mirrors.tuna.tsinghua.edu.cn/anthon/os-mipsel/os3-dpkg  InRelease
  Could not resolve host: mirrors.tuna.tsinghua.edu.cn
Err:2 https://mirrors.tuna.tsinghua.edu.cn/anthon/os-noarch/os3-dpkg  InRelease
  Could not resolve host: mirrors.tuna.tsinghua.edu.cn
Reading package lists... Done
Building dependency tree       
Reading state information... Done
All packages are up to date.
W: Failed to fetch
https://mirrors.tuna.tsinghua.edu.cn/anthon/os-mipsel/os3-dpkg/InRelease  Could
not resolve host: mirrors.tuna.tsinghua.edu.cn
W: Failed to fetch
https://mirrors.tuna.tsinghua.edu.cn/anthon/os-noarch/os3-dpkg/InRelease  Could
not resolve host: mirrors.tuna.tsinghua.edu.cn
W: Some index files failed to download. They have been ignored, or old ones
used instead.

root [ autobuild3@master ] # wget google.com
--2016-09-21 01:13:18--  http://google.com/
Resolving google.com (google.com)... failed: Temporary failure in name
resolution.
wget: unable to resolve host address 'google.com'

The weird part is that ping google actually works normally:

root [ autobuild3@master ] ! ping google.com
PING google.com (205.213.108.170): 56 data bytes
64 bytes from 205.213.108.170: icmp_seq=0 ttl=57 time=9.494 ms
64 bytes from 205.213.108.170: icmp_seq=1 ttl=57 time=9.088 ms
64 bytes from 205.213.108.170: icmp_seq=2 ttl=57 time=9.432 ms
...

In case you are wondering, here is my resolv.conf:

root [ autobuild3@master ] # cat /etc/resolv.conf 
nameserver 8.8.8.8

In addition to that, using wget with -4 parameter can work around this issue:

root [ autobuild3@master ] # wget -4 google.com
--2016-09-21 01:14:43--  http://google.com/
Resolving google.com (google.com)... 205.213.108.170, 205.213.108.162,
205.213.108.177, ...
Connecting to google.com (google.com)|205.213.108.170|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://www.google.com/ [following]
--2016-09-21 01:14:43--  http://www.google.com/
Resolving www.google.com (www.google.com)... 205.213.108.147, 205.213.108.172,
205.213.108.162, ...
Reusing existing connection to google.com:80.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: 'index.html'

index.html                        [ <=>                                        
  ]   9.94K  --.-KB/s    in 0.001s  

2016-09-21 01:14:43 (13.9 MB/s) - 'index.html' saved [10179]

P.S.: Everything worked as expected when Glibc 2.23 was installed, no system
configurations were changed before and after the update. I did not encounter
the same issue with other architectures: ARMv7, ARMv8, PowerPC, PPC64, AMD64.

P.P.S.: Glibc 2.24 was built with -O3.

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