Comment 239 for bug 417757
Revision history for this message
| strel (d-mestetskiy) wrote Re: [Bug 417757] Re: [karmic regression] all network apps / browsers suffer from multi-second delays by default due to IPv6 DNS lookups | #239 |
I have a wired connection. And I recently changed my modem to a much newer
one. I've been having issues recently, which seemed to spawn from an updated
vbox. I have ubuntu running as quest on windows 7. After the update of vbox,
my connection would be very strange, at start up of Firefox, everything
would load. After couple seconds or so, the connection would grind to a
halt. Recently, I activate IPV6 on Firefox, and the problem has gotten much
much better, but not completely alleviated. Some pages are constantly trying
to load, but never get there. But thats much better than before. Before I
switched the flag in Firefox, pretty much all the pages would be stuck in
load mode, it was so frustrating.
Specs:
Windows 7 with ubuntu guest through vbox
wired connection straight to the modem, nothing in between.
Windows 7 seems to work fine
Ubuntu seems like there are some issues still.
On Mon, Feb 22, 2010 at 5:19 PM, Yermo <email address hidden> wrote:
> @Laurent No. Wired connection exclusively.
>
> --
> [karmic regression] all network apps / browsers suffer from multi-second
> delays by default due to IPv6 DNS lookups
> https:/
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in “eglibc” package in Ubuntu: Triaged
> Status in “network-manager” package in Ubuntu: Invalid
> Status in “eglibc” source package in Lucid: Triaged
> Status in “network-manager” source package in Lucid: Invalid
> Status in “eglibc” source package in Karmic: Fix Released
> Status in “network-manager” source package in Karmic: Invalid
> Status in “glibc” package in Fedora: Confirmed
>
> Bug description:
> In Karmic, DNS lookups take a very long time with some routers, because
> glibc's DNS resolver tries to do IPv6 (AAAA) lookups even if there are no
> (non-loopback) IPv6 interfaces configured. Routers which do not repond to
> this cause the lookup to take 20 seconds (until the IPv6 query times out).
>
> *** PLEASE DO NOT COMMENT ON THIS BUG unless you have something
> constructive to say. Everything that can be said has already been said, and
> if you comment, you are just adding noise. Please let those that actually
> know what they are doing concentrate on fixing this bug from now on. ***
>
> To unsubscribe from this bug, go to:
> https:/
>
--
Dmitriy Mestetskiy