Hi, After a lot of searching, on about the 83rd page of results from one of my google searches, I think I may have found the answer. There are some internal resolver variables which can be set to control the length of time the system will wait before retrying the name server lookup, and the number of retries which will be attempted. These can be set in resolv.conf. I have added retrans:60 retry:4 and this has solved my problem. BTW, retrans is doubled for each retry, so my value of 60 is probably too high, and will lead to delays if my ISP's primary DNS is down. I set it to this just to ensure there was no chance of the resolver giving up before the connection was up and running. I think that the default sytem values are retrans:5 retry:4, so the whole process would timeout after 5 + 10 + 20 +40 = 75 seconds. In my case, the dialup and connection process to my ISP takes about 90 seconds, so you can see why I was getting a timeout. Like you, my connection was up and running long before getting the browser timeout message. You can see from the above that if the resolver has already given up before the connection to the nameserver is established, the browser will eventually timeout 'cos its DNS query never gets answered. I was fooled for a while because I did not get the error with Konquerer but did with Mozilla/Netscape/Galeon. Maybe Konquerer resends the query if it gets no reply, and Mozilla doesn't. One page which I have found is http://www.csuglab.cornell.edu/cgi-bin/da10/man.cgi?section=4 <http://www.csuglab.cornell.edu/cgi-bin/da10/man.cgi?section=4&topic=resolv. conf> &topic=resolv.conf BTW this information does not appear in man resolv.conf on my system. Good Luck, Darrell. -----Original Message----- From: Michael Andersson [mailto:micand@vh.volvo.se] Sent: 11 August 2001 13:28 To: 'Kavanagh, Darrell' Subject: SV: [SLE] Dial on Demand Hi! I´ve had the exact same problem for quite some time now. Although this on the Windoze-boxes on the LAN that has this problem. I didn´t think this was browser-related but rather network-related and have been trying to find some info on a solution without any luck. The windoze-boxes all use IE. If you find something out I´d be glad if you drop me a line. I´ll do the same if I find something out. By the way, I have a ISDN-connection so I don´t think I have a timeout problem. The ISDN-connection gets up and running long before I get the timeout-error in the browser. BR Mike A -----Ursprungligt meddelande----- Från: Kavanagh, Darrell [mailto:Darrell.Kavanagh@newellandbudge.com] Skickat: den 9 augusti 2001 15:39 Till: suse-linux-e@suse.com Ämne: [SLE] Dial on Demand Hi everyone I've just got SuSE 7.2 (kernel 2.4.4) installed on my home pc and have configured dial-on-demand to connect to my ISP (dynamic IP addressing) using the supplied wvdial.dod script. Everything works fine (almost). When using any flavour of Netscape or Mozilla, and Galeon, the first request to a remote site when the modem is down does not work. The "not found" message comes back after modem has connected. Hitting the refresh button after this has no effect, but refreshing the URL by double clicking the address then hitting enter loads the site immediately . The puzzling thing is that if I use Konquerer, I do not get this problem. This browser somehow waits until the IP connection is established - maybe it is sending the initial request multiple times, rather than just waiting for a response to the first until it times out as the other browsers/mail clients seem to do. Or maybe the time out settings are different. I have tried the various suggestions regarding ip_dynaddr and aysnc dns for Netscape/Mozilla, with no effect. I have also tried using ip_resend, the utility shipped with my dist. I am thinking that tweaking the Mozilla preferences might help, although I have already tried putting massive numbers into any which seem to relate to timeouts for DNS, IP, HTTP etc, without any success. Could it be that I need to repeat the request after a specified time if no reply is received, and can this be set anywhere in the Mozilla conf files? Does anyone know their way round the Mozilla config files? Many thanks, Darrell. ******************************************************************************** This electronic mail system is used for information purposes and is not intended to form any legal contract or binding agreement. The content is confidential and may be legally privileged. Access by anyone other than the addressee(s) is unauthorised and any disclosure, copying, distribution or any other action taken in reliance on it is prohibited and maybe unlawful ********************************************************************************