Hello all, I'm using Mozill build M13 (2000012520) and have found that if I don't connect to the internet via dialup before I start Mozilla, Mozilla will not be able to resolve any hosts - even after I start a dial up session. In order to have Mozilla resolve any hosts, I have to close the application and start over. The exact error message is displayed in an Alert box and says "<HostName> could not be found. Please check the name and try again." where <HostName> is the web site that I had tried to access. Netscape 4.61 does not display this behaviour. It is able to resolve host names after a dialup session is started, even if it was started first. This leads me to believe it is a Mozilla problem. My environment: Red Hat Linux 6.1 KDE 1.1.2 Mozilla M13 KPPP dial up application Thanks David

Updating component.

reassigning to component owner.

Hmmm.... I know DNS isn't caching anything. The only thing I can think up of is that the error is being cached... assigning to gordon

dns should time out.

Moving post beta bugs to M18 which is now the post-beta milestone.

This also happens if midway through a session you close a dial-up connection then dial a different server using a different DNS server. The only around it is to restart Mozilla. I'm not sure how related these bugs are, or whether a new bug should be reported, so I'll leave that up to someone who knows these things. I get this problem using the same setup as the original reporter. (Except for the build no.: 20000041811

Happens on Mac OS builds (M18 2000092008) as well. Platform/OS to all? Not sure if this happens on Windows too. In the practical world of dialup internet connections, this is a major pain as you can't disconnect to make a phone call (or whatever) and then reconnect w/o restarting Mozilla.

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

Verified dupe.

The target duped bug was Mac-only. REOPENING: Gordon suggested to me once that this might not have to do w/ DNS but w/ some other initialization or reseting of connections.

+mostfreq

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

Ben, do you still see this as a problem on Windows and Linux?

I have this problem in Windows w/ SERA (netscape VPN software). See Bug 73346 . This report is about Linux.

Is anything happening with this bug? I have this problem with 0.9.6 on Windows 2000. If I start Mozilla and I am not connected to the network, it silently fails to connect to my homepage (www.google.com). Once I have dialled-up then reload has no effect and neither does typing in other addresses. The only way to connect is to re-start mozilla.

I just realised and verified that this means that Quick Launch can't be used in combination with a dial-up network connection. With quick launch enabled the browser starts up at log-in, before the connection to the network is made. If you connect to the network, then launch mozilla via the quick launch icon it is not possible to connect to any page. Shouldn't this be nominated for mozilla 1.0.

Nominate it for "mozilla1.0" :) Put it into the keyword field...

I tried, it appears that I don't have the correct permissions to change the keyword field of the bug.

clearing future milestone and nominating. I agree this should be addressed before 1.0.

I filed a similar bug somewhere, but the most likely cause (and you should try this out), is that DNS values are loaded at startup and not refreshed. The way to tell is to do the following: 1- Connect to network 1. Get everything working. 2- COnnect to network 2. Verify things don't work. Then try something by IP only. (www.packetgram.com is currently 63.201.57.29, if you are too lazy to look anything up). There could be other hidden dependencies when we switch network, which is why I haven't aggressively duped all these reports in the "need to refresh DNS cache" bug.

I tried using the IP address - that doesn't work either.

sigh. (guess it isn't a dupe.)

bug 64857 and bug 88144 seems to be dups of this?

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

If you used the IP address, then it isn't a DNS problem.

Let's assign it to gagan :)

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

Nominating for nsbeta1, as a user should be able to start Mozilla before she dials-in, and enters a URL.

We need to get the overall behavior working for network changes, no matter what the underlying problems are. I've updated the duplicates to see if anyone can clarify the DNS-only vs. IP addresses fail aspect of this bug.

dup of 64857. duping this one against the newer one cause the newer one has more critical data. *** This bug has been marked as a duplicate of 64857 ***

David: I tested in my environment, and if I switch networks, IP addresses work, but DNS does not. Can you provide steps that would suggest there is a IP related problem when we switch networks? If not, I'm going to verify this bug as a duplicate.

I'm not sure if this bug belongs here now! Build 2002030116 Here's the steps I take: 1) Login into windows 2000, standalone PC with no network connection 2) Launch mozilla 3) Connect to ISP through windows dial-up networking 4) Enter http://63.201.57.29/ into URL bar and hit return - nothing happens However, when I open mozilla mail then it connects to my pop3 server with no problem at all, I can also download messages from the news server too. So, the networking is obviously working it's just the browser that it is failing.

I found the source of the problem that I had, I have filed bug 133108. As far as I'm concerned this bug can be verified as a duplicate.

After going full circle on this bug, I'm reverting it to Linux-only. The Windows issues (mine and David) went to separate bugs. This bug is actually the last of a chain of dupes, so warp to bug 166479 for the final story).