Some domains don't resolve.
Barry Margolin
barmar at alum.mit.edu
Sat Jun 7 02:48:22 UTC 2008
In article <g2aeee$1bb9$1 at sf1.isc.org>, Kevin Darcy <kcd at chrysler.com>
wrote:
> Barry Margolin wrote:
> > But if your ISP has 100,000 users of the same caching server, it will be
> > cached if any of 1,000 users have accessed it recently. For any one of
> > them, there's only a 0.1% chance that their lookup will be the one that
> > has to wait for fetching from the source.
> >
> And if you have 100,000 users using the same caching server, it's likely
> to experience big spikes of activity (e.g. several thousands of queries,
> within the course of less than a second), during which time some users
> will experience some extra delay in getting their queries resolved.
Certainly if the nameserver is not engineered to handle the load it's a
bad idea to use it as a forwarder. That's a completely different issue
than whether it's useful to share caches via a forwarding hierarchy.
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***
More information about the bind-users
mailing list