Closed Bug 162435 Opened 23 years ago Closed 23 years ago

Conn:DNS: Laptop changing network => still uses old nameservers

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED DUPLICATE of bug 166479

People

(Reporter: zap, Unassigned)

Details

I just tried build 2002072204 on my Linux Laptop and it seems to hang network access whenever I change my network setup significantly: I run wireless both at work and at home and have a script which detects this at wakeup from sleep and adjusts my IP from 192.168.14x.x to 192.168.254.x (not DHCP) including routing etc. Mozilla can still work in offline mode and with local files when this has happened, but whenever I enter a network url it displays the "Resolving host ..." message for ~30 second and then an alert with "... could not be found. Please check the name and try again". Restarting the browser helps. Netscape 4.79 has no problem with this - my calender program (Steltor/Oracle) gracefully tells me that the connection is not available and exists. Wild theory: Netscape has some kind of DNS-helper process which perhaps solves change of local IP address in it's own way? I *think* that I didn't experince this last time I used Mozilla a while back (the reason I went back to NS 4.7x was just LDAP support which now seems to be just about up to par - great work!)
a blocker is a bug that "Blocks development and/or testing work" Since there is an obvious workaround in this case, and development is not blocked: Lowering severity.
Severity: blocker → normal
related/dup of bug 151683
BTW: Even after the problem has appeared, I can open the LDAP entry in the Address Book and access information online - so it's not ALL networking from Mozilla that is dead, just browsing. In case you consider it important: My laptop runs a fairly new Mandrake 8.2 installation with just a handful of additions (Mandrake's official kernel update, NS 4.79, above mentioned Mozilla to mention the significant ones). (Sorry about the "blocker" misunderstanding - it sure blocked all further browsing...)
About dup: I agree that it seems quite related, but in my case I never (normally) touch the "Work offline" button as I never DO work offline - the laptop is just asleep when I move between the two locations and I soon as I come out of sleep, the network is rearranged to the the new setup. Perhaps bug 151683 is a special case of this more generic problem?
as you see in that bug, the "offline" mode in mozilla has nothing to do with it. I believe this is a duplicate.
Hmm, if you refer to this bit from bug 149733 I will tend to agree: > Comment #3 From Kai Lahmann 2002-08-04 19:24 ------- > we have tons of bugs for not seeing a changed DNS, but I can't > find any right now ... > Comment #4 From Benjamin Chuang 2002-08-04 22:02 ------- > I'm hoping to clean this up next week... My changed setup does include a change of DNS. "Next week" seems to be about now...
Can you try an IP only case? (use nslookup to find the ip address of the hostnames in your URLs).
Summary: Laptop changing network => Mozilla hangs → Conn: Laptop changing network => Mozilla hangs
Sorry, I seem to have missed the mail with your question about plain IP. I can't verify 100% until tonight when I get back home, but I'm fairly sure that it should work. The reason I think so is that I can tell from my home ISDN router at home that Mozilla produces IP packets for the work DNS when it was originally started at work. I'll verify tonight (in ~12 hours).
Confirmed: Surfing on IP address only works after change of DNS. In fact, the Mozilla DNS resolver appears to be able to use the internal cache still, as I could keep surfing *WITHIN* the same site (sourceforge.net for instance) that I had resolved just before leaving the original network. Sites that I haven't visited since I started mozilla all fail. The conclusion seems to be that it is indeed a failure to notice a change of DNS. Not really a dup of bug 151683 (at least the the description of it), but I would expect both problems to go away whenever the DNS problem is resolved. Which bug# do you suggest that I track for this?
For the record: I just tried out 1.1 and the problem is still there. Exactly as before, plain IP addresses work (with sites that do not require 1.1 for site switching).
Summary: Conn: Laptop changing network => Mozilla hangs → Conn:DNS:: Laptop changing network => still uses old nameservers
There are Linux version issues to this feature working. Please see the bug, and inquire about how your version would be affected. Once you get this working, or if you get a clear answer there, please mark this VERIFIED. *** This bug has been marked as a duplicate of 166479 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Summary: Conn:DNS:: Laptop changing network => still uses old nameservers → Conn:DNS: Laptop changing network => still uses old nameservers
Yup - sure looks like this is what I experience on my system.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.