Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 48935 - Gentoo causes firefox to dns-resolve via 127.0.0.1
Summary: Gentoo causes firefox to dns-resolve via 127.0.0.1
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: High major (vote)
Assignee: Mozilla Gentoo Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-25 05:35 UTC by Felix von Leitner
Modified: 2004-11-13 15:55 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix von Leitner 2004-04-25 05:35:41 UTC
Mozilla Firebird from CVS and all versions of Firefox, when compiled on Gentoo (including firefox 0.8 via ebuild) ~x86 break horribly because they resolve about one in four DNS queries not via the name in /etc/resolv.conf but via 127.0.0.1.

This appears to be caused by Gentoo because working firefox binaries from a non-gentoo system also break on Gentoo.

My guess is that the Gentoo glibc updates somehow caused this through some sort of non-obvious interaction.  I have this problem for more than a year now, but did not report it because I thought it was a mozilla issue.  Now I have seen the same problem on a Gentoo system from a friend.  He works around by running a BIND on 127.0.0.1, I started using a local HTTP proxy.  Please fix!

I reported this a white ago to the Mozilla people but they were unable to reproduce it and so could not do anything about it.
Comment 1 Joseph Booker 2004-06-05 17:22:41 UTC
exactly what dns queries is it doing? does 'mv .phoenix .phoenix_old' help?
Comment 2 Felix von Leitner 2004-06-06 01:41:15 UTC
Queries for the web pages I want to go to.
A new profile does not help.
Comment 3 Aron Griffis (RETIRED) gentoo-dev 2004-11-13 15:55:44 UTC
I have never seen this on multiple arches.  Hopefully it is fixed for you presently with the current version (presently firefox-1.0-r1), but if not, please re-open the bug.