on Sat, 2 Feb 2008
14:10:43 -0800
> > There's your answer. I suspect you have a forgotten bogus entry in HOSTS.
> > I can only guess why Seamonkey is not bothered by it.
>
> I should have looked into RESOLV2 before I sent the previous post. It contains:
>
> domain
> nameserver 192.168.1.1
>
> 192.168.1.1 points to my router not a name server. Unless it must point there so the router can do
> its NAT thing. Perhaps SeaMonkey looks at some other source for direction.
I think the router can forward the DNS request to the real DNS server but that
extra delay may be part of the problem. I looked at the traces you sent and
one had a DHCP broadcast that had 192.168.1.1 as option 6 which is the name
server. It would work much better if the real DNS server was listed instead of
192.168.1.1. Check your router and see what it has as the DNS server
addresses. Then either put that in the TCP/IP setup or edit the resolv2 file
and replace the 192.168.1.1 with the real DNS server IP, if the router has two
addresses then add the second to the resolv2 (you would then have two
nameserver lines in the file).
--
Robert Blair
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 02 |
February |
2008 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
