Jeremy Wadsack wrote:
>
> Jim Sander wrote:
>
> > <snip>
> >
> > For example, you resolve 207.239.68.10 to "trelane.addy.com". You cache
> > this name, and when you get a request from 207.239.68.9 you determine
> > that 207.239.68.* is "addy.com" and have done with it.
> >
> > Of course this system isn't perfect since not all domains are broken up
> > along class C network boundaries, but it would speed things up somewhat
> > (DNS lookups longer than everything else analog does combined) and it's
> > close enough since I'd bet that most of those "oddball" sites don't
> > originate traffic anyway.
> >
> > Anyone else think about this and find something I haven't?
> Aside for STEPHEN: Again, how about a page for links to these things? "Analog
> Configuration Resources"
yep...i'll be more than happy to keep the list for people..i'm going to
anyway
but if people want to send me more ... i'll maintain it...
pac
--------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
--------------------------------------------------------------------
