From: "Geo" 

"Mike N."  wrote in message
news:mvm2c2df0ltuglhes1mto766i9tjjcpe8s{at}4ax.com...

>    I asked them, and they do not fiddle with the TTL setting.

Then they have the same cache as everyone else.

>   Caching just comes from a large population of users and a large RAM
> cache.  When querying an OpenDNS server with a million users, www.nls.net
> is more likely to already be in cache than my local DNS server.

www.nls.net has a 3 hour TTL so it's unlikely to be in cache for the second
query. And since a large population of users and a sluggish dns server seem
to go hand in hand, I still feel this is 99% marketing. Oh and the RAM
comment, anyone with a million users hitting a dns server, is going to be
running maximum memory anyway.

One thing that might be possible (I've never tried this but I know I can
set it up in NT's dns manager) is that they might set the cache so it's
shared between machines, replicated like a primary/secondary/secondary type
set of servers where the secondaries are set as resolvers so that their
busiest box replicates the cache out to resolvers. That way they could have
an unusually large number of users hitting the primary dns server and have
the secondaries doing all the work when it's not in cache. dunno if that
would gain you anything but it should be possible to configure.

Other than that, I smell lutefish in their claims .

Geo.

--- BBBS/NT v4.01 Flag-5