Bug#632273: libc6: resolving: does not try different nameserver after recursion not available

tag 632273 - upstream tag 632273 + unreproducible thanks On Thu, Jun 30, 2011 at 11:45:19PM -0500, Jonathan Nieder wrote: Package: libc6 Version: 2.13-8 Tags: upstream Typical amd64 experimental system. No ipv6 in sight. Since the last upgrade[*] (libc6 2.13-7 - 2.13-8), programs like

Bug#632273: libc6: resolving: does not try different nameserver after recursion not available

# I can still reproduce it. tags 632273 = moreinfo quit Aurelien Jarno wrote: On Thu, Jun 30, 2011 at 11:45:19PM -0500, Jonathan Nieder wrote: That is, the crazy wireless router in this wireless network provides a nonrecursive DNS server through DHCP and although resolv.conf also includes

Bug#632273: libc6: resolving: does not try different nameserver after recursion not available

# Aurelien Jarno wrote: # # tag 632273 - upstream # # After downgrading to 2.13-7, it works fine again. Then reproduced # with 6f8326ca (Fix robust mutex handling after fork, 2011-07-30), # built by # # $ mkdir build # $ cd build # $ ../configure --prefix=$HOME/opt/glibc-latest # $ make # $

Bug#632273: libc6: resolving: does not try different nameserver after recursion not available

Jonathan Nieder wrote: After downgrading to 2.13-7, it works fine again. Then reproduced with 6f8326ca (Fix robust mutex handling after fork, 2011-07-30) Bad tcpdump: | 08.668827 IP 172.16.1.35.58800 homeportal.gateway.2wire.net.domain: 64142+ A? repo.or.cz. (28) | 08.668887 IP

Bug#632273: libc6: resolving: does not try different nameserver after recursion not available

Package: libc6 Version: 2.13-8 Tags: upstream Typical amd64 experimental system. No ipv6 in sight. Since the last upgrade[*] (libc6 2.13-7 - 2.13-8), programs like wget that use getaddrinfo are failing resolution instead of resolving some hosts: | $ wget http://repo.or.cz/ | --2011-06-30