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

[Jonathan Nieder <jrnieder@gmail.com>]

# 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 8.8.8.8 for sanity, and the updated libc doesn't seem to use
>> the latter any more.
[...]
> This upstream bug report is indeed your bug, but the corresponding patch
> is actually backported into 2.13-8. I am able to reproduce your problem
> with 2.13-7, but *not* with 2.13-8. Is there any other condition to be
> able to reproduce the issue? Can you try with another non-authoritative 
> name server instead of the one provided by your wireless router?

I am _not_ able to reproduce the problem with 2.13-7 but _am_ with
2.13-8; I pointed to that upstream bug report because I assume that
the patch used to fix it introduced this problem.

Also, I should clarify that the name server on this wireless router is
completely insane, and it may be that relying on

	append domain-name-servers 8.8.8.8;

in /etc/dhcp/dhclient.conf to correct the damage while still allowing
authentication on other wireless networks that play tricks with DNS to
log in was too much to hope for.  I reported the bug because it's a
regression.

The router is a 2Wire HomePortal 1000SW, firmware version 3.5.1, for
what it's worth.  I don't know what software it uses to provide DNS or
if there is a public DNS server exhibiting the same problem.

Sorry for the lack of clarity, and hope that helps.