104857 - Conn: Mozilla returns "unresolved host" rather than wait for dialup

Status: VERIFIED DUPLICATE of bug 150729

(Core :: Networking, defect)

Description

[Mark Leverson]

I have:
500 mhz Indigo iMac, 384 mb ram, OS 9.2.1 and OSX 10.1, 56K internal modem,
CD-RW, Lexmark Z53, Earthlink ISP, dial up service, Mozilla OSX 0.9.4 Build ID:
2001091313


The problem on inital launch is duplicatable by double clicking Mozilla OSX
0.9.4 with the phone connection in a disconnected state. Mozilla brings the
start page URL into the window, it dials the ISP, connects, then sits there
trying to resolve the host, and eventually says that it can't find it. The
reload button doesn't work at this point. You can double click on the URL window
and then return and Mozilla will go to the URL site. I have
http://start.earthlink.net set as my home page. It doesn't seem to be site
dependant however. This can happen on any site that you try to go to from a
state of your phone connection being disconnected.

Comment 1

[Bradley Baetz (:bbaetz)]

Does this happen on os9, or only osx?

Does going offline, then online, fix this?

Comment 2

[benc]

Mark: is this new summary accurate?

Comment 3

[Mark Leverson]

Ben: Yes the summary is accurate.

Brad: This is an OSX version. Once the phone line is connected mozilla will go
to any URL.

Comment 4

[Bradley Baetz (:bbaetz)]

Then this is the resolv.conf thing, I guess. Going offline and then online may help.

Dupe of bug 63564 - also see bug 64857.

*** This bug has been marked as a duplicate of 63564 ***

Comment 5

[Mark Leverson]

It looks like bug 64857 is on a Linux Operating System. So I'm posting it here too.

I just downloaded Mozilla OSX 0.9.5 and the problem is still there.

Comment 6

[Greg K.]

Mark, can you still reproduce this problem under 0.9.6?

Comment 7

[Mark Leverson]

Greg:  Yes, this bug is still present in Mozilla 0.9.6 .  I just downloaded it
and have MRJPluginCarbon-1.0d6 installed now also.

Comment 8

[John Levon]

The "reload" not working is bug 97641 or an earlier one I think ...

Comment 9

[Greg K.]

Is this still a problem using RC1?

Comment 10

[Mark Leverson]

Greg, Yes this is still a problem. The error message has changed though. It now
just times out, with bringing up the URL.

Comment 11

[Greg K.]

Mark, it appears a related bug (bug 117628) was fixed for 1.0. Do you still see
this problem using either 1.0 or 1.1a?

Comment 12

[benc]

Actually this is a Mac OS X thing from the looks of it. 

The browser will succeed on the second try (w/o quit+relaunch). The reload
button does not work because it is primed only on a successful load. This
problem does happen with IP as well, so the DNS failure is a network error. I
also think that 117628 was not affecting Mac OS X, b/c if it did, then you would
have had to quit+relaunch to get DNS working.

Mark, please look at the duplicate bug, and see if it accurately describes the
behavior you see (I have it in Mozilla 1.0)

*** This bug has been marked as a duplicate of 150729 ***

Comment 13

[Mark Leverson]

This bug is still affecting me in 1.0.0. If I just launch Mozilla wihout having
the internet dialup connection already made, it won't go to my start page. It
responds saying the site can't be found. I have no trouble getting the site if I
just put the recall URL from a bookmark. I don't have to relaunch Mozilla.
150729 is much closer to what I have.

Comment 14

[benc]

Right. You are a dupe of bug 150729, which is open and confirmed for your build.

(Normally I like to dupe back to the lowest bug number, but in this case, the
best analysis of the problem is there, so I'm duping your bug to that bug.). If
you see any differences in the behavior between the original bug I dupe to, and
your bug, please note it here.


*** This bug has been marked as a duplicate of 150729 ***

Comment 15

[Matthias Versen [:Matti]]

verified dupe