Date: Sat, 13 May 1995 18:51:09 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: henrich@crh.cl.msu.edu (Charles Henrich) Cc: davidg@Root.COM, henrich@crh.cl.msu.edu, freebsd-bugs@freefall.cdrom.com Subject: Re: bin/402: w -n doesnt work as advertised. Message-ID: <199505140151.SAA01112@gndrsh.aac.dev.com> In-Reply-To: <199505132239.PAA14255@freefall.cdrom.com> from "Charles Henrich" at May 13, 95 06:38:55 pm
next in thread | previous in thread | raw e-mail | index | archive | help
>
> > This works if the nameserver for all the domains is currently reachable. If
> >it isn't, it can take a minute for the query to timeout. About half the time I
> >do a 'w' on freefall, it takes > 1 minute to complete because of this. In
> >other cases, it's often that nameservers are slow to respond - 2 seconds isn't
> >unusual for non-cached entries. If this happens with just a few of the users,
> >the delay can approach 5-10 seconds. The problem grows as the number of users
> >increases. It's extremely annoying.
>
> Thats true, but if the user has logged in, they have caused their entry to be
> cached at the local nameserver, so you should very rarely be going offsite to
> get the data.. Unless something is broken in the local nameserver.
^^^^^
More often than not, it is broken in the remote nameserver, so that even
the login takes a long time as it too does the lookup. Also, again, folks
who sit behind certain firewalls don't ever have a reverse lookup (something,
IMHO that should be outlawed requireing at least some kind of outside
DNS server exists to return fictitious names, ie 2 views of the world DNS
firewalling).
--
Rod Grimes rgrimes@gndrsh.aac.dev.com
Accurate Automation Company Custom computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199505140151.SAA01112>