[bind10-dev] recursor cache requirements - input required

Jerry Scharf scharf at isc.org
Thu Dec 9 06:03:28 UTC 2010


On 12/8/2010 9:40 PM, Likun Zhang wrote:
>> All these classes except for hesiod are defunct AFAIK. Hesoid is used at
>> MIT but I don't think that hesiod was carried over to MS active
>> directory. As such, I would set up the default to allow IN and HS and
>> not allow the rest. None and any are not cached. Chaos net is long dead.
>> The bigger problem with cache instancing is when people have multiple
>> views. One person in the user survey reported having 100 views on one
>> machine. Not surprisingly , he complained about memory footprint.
>> (Patient: "doctor, it hurts when I do this." Doctor: "stop doing it.")
> We are talking about the recursor cache, does the pure recursor need to
> support view? I don' think so.
>
> Likun
>

Yes, almost all servers running with views are recursive. They will also 
typically have some auth data, but the biggest part is that the view 
caches need to not pollute each other with data. The general model is 
the the inside view needs to cache the internet data plus the private 
network data for all the inside connections. The outside view needs to 
cache just the outside data for the bastion hosts' external interfaces.

jerry




More information about the bind10-dev mailing list