Hi!
The cache needs to be big enough that it has a thrashy bit that is
getting changed all the time. Those are the records that go into the
cache and then die without being queried again. If the problem is
that there's some other record in there that might be queried again,
but that doesn't ge
On 8/17/12, Michael Thomas wrote:
> If the dnsbl queries are not likely to be used again, why don't they
> set their ttl way down?
Because the DNSBLs don't tune the TTLs for individual responses; they
likely still benefit from extended caching, high TTLs for responses
makes sense for controlling
On Aug 18, 2012, at 5:35, Raymond Dijkxhoorn wrote:
> Reverse DNS isnt the only issue here. There are many sites that give each
> user a subdomain. And if i look at my top talkers on some busy resolvers i do
> see that thats doing about 25-30% of the lookups currently.
>
> akamai.net, amazonaw
On Aug 18, 2012, at 8:44, Jimmy Hess wrote:
> And I say that, because some very popular RRs have insanely low TTLs.
>
> Case in point:
> www.l.google.com.300INA74.125.227.148
> www.l.google.com.300INA74.125.227.144
> www.l.google.com.300INA74.125.2
4 matches
Mail list logo
