Closed
Bug 1147547
Opened 11 years ago
Closed 10 years ago
/etc/hosts problem
Categories
(Core :: Networking: DNS, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 705483
People
(Reporter: hermans, Unassigned)
Details
(Whiteboard: [necko-backlog])
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150306135748
Steps to reproduce:
On top of my normal xubuntu setup, I run a vpn solution in shells, and generally hand-wire my network connections back to my place of work. I have to, because support for the particulars is sketchy (pkcs11 token and all that). But it *works*. For *every* application, the routing table, /etc/resolv.conf, is enough. They work. Even Thunderbird works just fine: I can read my emails from work through this convoluted setup just fine.
Just not firefox. Firefox seems to live in a completely different network reality. It doesn't resolve the names for the intranet that I give it at all. Restarts, waiting, it doesn't help a bit. Oh, internet names are fine, just not something that resides on intranets.
Actual results:
I typed in the name of a http server that resides on my company's intranet, which I can reach fine through a) being in the intranet, b) on other browsers on other operating systems, just not through firefox on xubuntu, even though all other applications (eg, cifs, thunderbird, pinging, telneting to port 80) work.
Expected results:
Firefox should have just used /etc/resolv.conf, which is what all the other applications seem to do.
Updated•11 years ago
|
Component: Untriaged → Networking: DNS
Product: Firefox → Core
Updated•10 years ago
|
Summary: Firefox resolves names differently from *everyone* else → /etc/hosts problem
Whiteboard: [necko-backlog]
Updated•10 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•