Tim: >> Try a different browser, just in case Firefox (or whatever else) has got >> it into its head that the site can't be reached, and it just isn't going >> to try again. Been there, done that, but don't have the tee shirt... Gene Heskett: > Now that's odd, seamonkey walked right in. WTH? Often that's down to browsers playing DNS games. The first time you try to access a site it may not get a DNS answer. It can cache that "no answer" just as it can cache the IP address from an answer. Sometimes it'll cache that answer for a ridiculously long time. There's two solutions: Close down the browser, and restart. This means all tabs and all windows, losing track of everything that you were doing. I haven't found any other way of doing this, it's not like the cached web pages which are deletable files on disc. Use another browser. It'll make a fresh DNS query, and hopefully get an answer. As to why you don't always get an answer when doing a DNS query? Who knows. It could be down to the DNS server having stupid settings (such as proxying servers on ISPs that don't check for fresh answers when they should). Or perhaps the DNS server with the answer is being deluged by queries for spam, and the like. One of my old ISPs forever seemed to have something seriously wrong with their DNS server. It certainly wasn't me. Several different computers, and several different OSs, all had the same issue: *More* often than not, news.optusnet.com.au wouldn't resolve. I had to put an entry for it in the hosts file. Querying their own DNS server would usually fail, and my own local DNS server couldn't answer for the same reason. -- (This computer runs FC7, my others run FC4, FC5 & FC6, in case that's important to the thread.) Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
