My DSL router also triggered this issue. I just want to add the note
that for me, getaddrinfo does occasionally return correct results,
indicating that the flakiness of the DNS server is timing dependent.
What a maddening problem to diagnose!
Andrew
--
To UNSUBSCRIBE, email to debian-bugs-dis
Actually i suspect this problem, which i see too btw. - dns lookups
taking too long - is the same thing a collegue had with his gentoo
workstation a few weeks ago.
The new glibc sends out two dns requests, one for IN A, and one for IN
at about the same time _and_ with the same source port:
1
Matijs van Zuijlen wrote:
>> If that is the case, could you try to disable IPv6 by blacklisting the
>> ipv6 modules.
>
> That didn't help.
>
>> Also can you try if a different server in resolv.conf
>> (e.g. the ones of your provider) in /etc/resolv.conf?
>
> That did, thanks.
I spoke too soon:
Aurelien Jarno wrote:
> Are you using your router for the DNS server? The new glibc fires out
> an A and a DNS query in parallel, and that some buggy DNS server
> return an error for the query using the id of the A query.
Yes, I am using my ADSL modem as the DNS server.
> If that is the
On Thu, Feb 19, 2009 at 10:13:38PM +0100, Matijs van Zuijlen wrote:
> Package: libc6
> Version: 2.9-1
> Severity: important
>
> After yesterday's upgrade of libc6 from 2.7-18 to new 2.9-1, and a reboot,
> almost all programs stopped resolving hostnames. Notable exceptions were
> ping and dig. Afte
Package: libc6
Version: 2.9-1
Severity: important
After yesterday's upgrade of libc6 from 2.7-18 to new 2.9-1, and a reboot,
almost all programs stopped resolving hostnames. Notable exceptions were
ping and dig. After comparing wget and ping source codes, and writing a
tiny test program, it became
6 matches
Mail list logo
