OK. A little more now in the way of advice ...
It seems (based on the lynx results you report) that the problem is that
your ISP's nameserver isn't responding to queries in a timely way. I should
have asked this before ... do other services that use DNS (telnet, ftp,
nslookup, etc.) also have problems when you use them with hostnames, or is
the problem limited to Web service?
If the answer is yes ... it looks to me like your local setup is right, so
I'd suggest you ask your ISP for additional nameservers to add to
resolv.conf (just for perspective -- my ISP supplies 3 nameserver addresses
to its customers).
If the answer is no ... then I'd suspect something to do with the way the
ISP has proxying set up. I recall you posted a separate message about use of
the proxy server, but I don't recall the details.
At 02:15 PM 12/10/99 Australia/Can, Sharon Elix wrote [in part]:
>Thank you so much for your help. Unfortunately, I haven't got much further and
>am feeling rather clueless. In response to your questions...
....
>> 8. How much time passes between the message
>> Looking up www.redhat.com
>> and the message
>> Unable to locate remote host www.redhat.com
....
>In Netscape, I get no connection after a very long time (more than 10
>minutes), as I've said it seems that Netscape freezes. No more moving stars
>and comets, and I can't close the program without using alt-ctrl-backspace in
>KDE. In Lynx, the failure to connect message comes up much more quickly, maybe
>1-2 minutes. I tried using a number of different remote hosts too, not just
>the red hat site.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
