I'll read up on named and give it a shot.  But it seems as though the
connection is made without probs to the internet www server.   Then it
takes a long time to actually get packets flowing to my LAN client.  I
would think that DNS isn't too much the culprit because the tcp connection
is established.  So from there DNS lookups wouldn't be all that common
since my NetNSD box already has the IP of the www host.  So maybe moving
the packets from the real internet IP over to a LAN IP is killing
it......just doing a straight ftp to the NetBsd box from the internet was
going at about 445 kbps last night.  But jumping to a client show more like
2 kbps.  It couldn;t load all of CNN's homepage before the in the 5-10
minutes I waited.

hmm...

Thanks
Keith

At 05:22 PM 7/12/99 -0400, you wrote:
>>Why would I run named or gatd?  Isn't my ISP taking care of that?  So I
>>just tell my client computers that the DNS address is the real cable modem
>>ISP address and the NetBSD forwards the packet to the modem since it isn''t
>>destined for a 10.0.2.x LAN computer.  Is that a bad idea?
>
>But you were complaining about bad response time...often, that's because a
>DNS server is slow in responding. If you run a local dns server, then you
>don't have to wait for the ISP's server to respond (as long as the addie is
>cached or you have some semblance of a SOA). For things like web pages,
>you're even screwed in that you can't check to see if it's a DNS problem by
>using dotted-quad...since the page itself will undoubtedly reference domain
>names for elements on the page. A DNS server can often be one of the
>biggest things you can use to speed up web access from your LAN.
>
>
>HTH
>Mike
>Bikers don't *DO* taglines.

________________________
Keith C. Fischer
Systems Administrator

POISONLAB, Inc.

kfischer@poisonlab.com
http://www.poisonlab.com