zbeinet wrote:
> When 2600 was up(could connect to the out world), the problem segment
> came back to normal.
> Someone said it was the DNS problem, but I don't think so, cause on the
> 192 segment ONLY mail
> was so slowly, but WWW was OK, and it also used DNS. Another reason is
> the arp command does not
> use DNS, is that right?
>
> I really wonder about it, Could anyone give me an explanation, what was
> wrong?
arp does use DNS. To NOT use DNS, use: arp -n
To test DNS, you can always use nsloookup, ie: nslookup www.netscape.com
Depending on caching, try hitting something you don't normally go
to..
I believe netscape caches DNS entries too..which might be why
it continued to work...but I may be wrong about that...
--
Ben Greear ([EMAIL PROTECTED]) http://www.candelatech.com
Author of ScryMUD: scry.wanfear.com 4444 (Released under GPL)
http://scry.wanfear.com http://scry.wanfear.com/~greear
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
