said:
Hi,
>I think the router can forward the DNS request to the real DNS server but
>that extra delay may be part of the problem.
Some routers can also act as a DNS cache.
If you are going to use the router as your DNS server, the router needs to
be configured with the correct DNS server IP addresses for the upstream
servers.
>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.
This is fine, if the router is properly configured to be a local DNS
server.
>It would work much better if the real DNS server was
>listed instead of 192.168.1.1.
At least for now. This requires that option 6 be disabled in dhcpd.cfg.
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 3.00 beta 10pre #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
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 [ 04 |
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.
