Closed Bug 1079217 Opened 10 years ago Closed 3 years ago

Extremely slow connection (DNS lookup?) on Ubuntu

Categories

(Core :: Networking: DNS, defect, P5)

32 Branch
x86
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1122907

People

(Reporter: djst, Unassigned)

Details

(Keywords: perf, Whiteboard: [necko-would-take])

I friend of mine pinged me about an issue he has with his Ubuntu computer running a fresh copy of Firefox. He has tried on multiple computers all with fresh Ubuntu and Firefox installs and they all excibit the same problem: connecting to websites takes a matter of 10-20 seconds before the page actually starts to load. It could be DNS related, but I'm not sure. A quick search revealed that many people have this issue on Ubuntu, and for some of them it seems that IPv6 is the culprit. Not in this case, though. For the record, see: https://support.mozilla.org/en-US/questions/957230 http://ubuntuforums.org/showthread.php?t=2160767 http://ubuntuforums.org/showthread.php?t=1547051 User Agent Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 Here is a quick video that he recorded to show the problem: https://www.dropbox.com/s/fxg4j9mqz7ist7v/firefox%20slow.ogv?dl=0. As you can see, the problem occurs every time a new page is loading.
I had similar problems. However, I realized that the problem was DNS settings on my system. For some reason, my resolve.conf settings didn't switch when I joined my home network and contained two nameserver entries that didn't exist on this network. The third nameserver in resolve.conf worked. As soon as I removed the first two and left just the good nameserver, this problem went away. I run Chrome on the same computer an it didn't have any problems loading pages speedily. I'm not sure Chrome does differently, but maybe Firefox could improve here.
Keywords: perf
Whiteboard: [necko-would-take]
Could be same as bug 1122907.
Component: Networking → Networking: DNS
See Also: → 1122907
Priority: -- → P5

Marking as duplicate of bug 1122907 because it contains 2 workarounds (although this kind of issue shouldn't occur in latest Firefox versions).

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
See Also: 1122907
You need to log in before you can comment on or make changes to this bug.