68085 - DNS: if started with wrong network settings, resolution never works

Status: VERIFIED FIXED

(Core :: Networking, defect)

Description

[Mike Pinkerton (not reading bugmail)]

- set your network settings incorrectly, such as selecting airport when you're
on ethernet (or vice versa)
- launch navigator and try to load a page (you'll hang for 30 seconds or so
trying to reach the non-existant dns server)
- hit stop
- change your network settings so they're correct
- try to load a page

expected:
- ot is smart enough to correct itself, should load the page 

actual:
- throbber spins, nothing happens. must quit and re-launch to load pages

as a side note, mail (imap) is smart enough to work correctly in this case.

Comment 1

[Simon Fraser [no longer active]]

Sounds like a situation where listening for the extra notifications in the 
notifier would be useful (see bug 67892)

Comment 2

[gordon]

If you read my comments in bug 67892, you would have seen that nsDNSService DOES 
listen for the extra notifications.  So does the NSPR DNS notifier.

Something else is happening here, because I tested the notifications by changing 
my network settings, and now it doesn't seem to work for pink.

Comment 3

[Matthias Versen [:Matti]]

*** Bug 75095 has been marked as a duplicate of this bug. ***

Comment 4

[Gagan]

even though getting this fixed is important this can wait till 0.9.2 

Comment 5

[dales]

There has been a change made in Mozilla Mac Build ID# 2001050408 that permits it
to resolve page requests after a broken net connection.  Up until Thursday
builds such connections would just not be made.

One other effect noted is that Mozilla will trigger Remote Access to dial for a
connection, which it didn't previously do.

Whatever happened, I hope it stays ... I don't mind 0.9.2 fixes arriving early.
 
Dale

Comment 6

[gordon]

Simon, did you make any changes that would have affected this?

Comment 7

[Simon Fraser [no longer active]]

Hrmm, I don't think so.

Comment 8

[dales]

I appears that this observation

> There has been a change made in Mozilla Mac Build ID# 2001050408 that permits 
> it to resolve page requests after a broken net connection.

appears to have been a phantom observation.  As of the 5/8 Mac builds (don't
have to specific number at hand now), the DNS failure after a broken net
connection is present.  I wasn't able to test in the 5/9 (roughly 10 am) build
due to an Installer failure ... but I wouldn't expect any different.

I certainly hope that Mozilla will get "educated" enough to ask for a net
connection when it finds that one doesn't exist.  Both Netscape Communicator
4.77 and IE 5 do this and iCab does a half-way job (doesn't request the
connection, but will pick up and use one established manually outside iCab.) 
Mozilla fails to do either of these; the only recourse is to Quit and relaunch
Mozilla.
Bad PR; bad mojo ;(

I will keep watching and testing this one.

Dale

Comment 9

[benc]

Open Networking bugs, qa=tever -> qa to me.

Comment 10

[dales]

I am now running Build ID 2001053108 (Mac, full installer).

I am successful in reestablishing connection to web pages after breaking the PPP
connection to the Internet.  I've tried two cases: (1) connection is manually
broken and manually reconnected independent of Mozilla ... a selected page will
then load (using a page not previously accessed in the current Mozilla session);
and (2) connection is manually broken then a new page is selected in Mozilla
which action triggers Moailla to query Remote Access to make a PPP connection
and then Mozilla requests the page.

This behavior had reappeared around May 8, went away, and has now reappeared in
the 5/31 build.  I do hope it stays put this time.
 
Dale

Comment 11

[gordon]

I believe this was fixed with the recent NSPR changes simon and I landed. 
Marking FIXED.

Comment 12

[benc]

Gordon, do you have a bug number for that NSPR fix?

Comment 13

[gordon]

NSPR Fix was in bug 69285.

Comment 14

[benc]

VERIFIED, CFM RIP.