Closed
Bug 1042788
Opened 10 years ago
Closed 10 years ago
Failing to resolved aliased host
Categories
(Core :: Networking: DNS, defect)
Tracking
()
RESOLVED
FIXED
mozilla34
Tracking | Status | |
---|---|---|
firefox31 | --- | unaffected |
firefox32 | --- | ? |
firefox33 | --- | ? |
firefox34 | --- | fixed |
People
(Reporter: nick, Assigned: sworkman)
References
Details
(Keywords: regression)
So I have an internal server on Mozilla's VPN. It's hardwired in, and has a static IP address. I have a link shortener [0] pointing to the host name. In Firefox Nightly, 34.0a1 (2014-07-23) and the build from yesterday, I haven't been able to resolve the host name, though I can just fine in stable 30.0 and in other browsers. The internal hostname IT gave [1] me seems to be an alias to another hostname [2] (found by running `host nick.corp.mtv2.mozilla.com`). My /etc/resolv.conf does contain the line `search mtv2.mozilla.com`. Others on nightly also can't see my server.
At first, I though maybe someone misconfigured the DNS tables on our VPN, but since it works in other browsers including FF 30.0, and I swore it worked in nightly a few days ago; this leads me to think that this is a regression
[0] http://mzl.la/nick
[1] nick.corp.mtv2.mozilla.com
[2] malta-athens-cairo.corp.mtv2.mozilla.com
Which versions of Firefox are affected by this bug? Did it first show up in Firefox 31?
Keywords: regression,
regressionwindow-wanted
Reporter | ||
Comment 2•10 years ago
|
||
Just upgraded stable to 31.0 (since it was just released a few days ago). Can't reproduce. Since we just incremented version numbers, I suspect 33.0+ as being affected (though 32 could be as well).
status-firefox31:
--- → unaffected
status-firefox32:
--- → ?
status-firefox33:
--- → ?
status-firefox34:
--- → affected
Reporter | ||
Comment 4•10 years ago
|
||
Further strange behavior, if I use the shortened link ([0] from description), I get the correct redirect but the aliased host fails to load ([1] from description). Using command+r to reload the tab fails. If I open a new tab and paste in the aliased host [1], it works! Going back to the first tab that failed, if I replace the url with [2] from above or the IP address, it fails to load in that tab. But, I can create a new tab and view them.
Assignee | ||
Comment 5•10 years ago
|
||
Nick, you might be experiencing a similar issue to bug 1041511. I just landed a patch on inbound a few hours ago, and there are try builds available. Can you try one of those to see if it fixes your issue? Thanks!
Reporter | ||
Comment 6•10 years ago
|
||
Marc Schifer also reports that in 30.0+, that if you leave a tab open for a while, then try refreshing it, suddenly it fails.
Comment 7•10 years ago
|
||
(In reply to Patrick McManus [:mcmanus] from comment #3)
> john -can you take a look at this?
I'll wait to hear how Steve's patch performs. I don't have any idea what could cause this off the top of my head.
Flags: needinfo?(josullivan)
Reporter | ||
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 8•10 years ago
|
||
Thanks for the help, all.
Updated•10 years ago
|
Updated•9 years ago
|
Keywords: regressionwindow-wanted
You need to log in
before you can comment on or make changes to this bug.
Description
•