[bind10-dev] recursor cache requirements - input required

[Mark Andrews]

In message <001701cb9b7f$f20e5ad0$d62b1070$@com>, "Likun Zhang" writes:
> Hi all,
> 
> I have updated the document of recursor cache according the comments from
> the bind10-dev list, the latest version is 8.
> 
> http://bind10.isc.org/wiki/RecursorCacheRequirements
> 
> There is one "Questions" section in the document, the only question is what
> the Key should be for the items in message/rrset cache
> 
> Shane's opinion is that only the class IN should be supported on the
> recursor cache, so the key for items in message/rrset cache will be
> "Query_name + Query_type". What shane said in his email is: Personally I
> really think we should just support class IN on the recursive side. CH is
> useful for getting ID.SERVER and the like, but nothing useful in the caching
> side, and the only other class is HS which MIT can send us a patch for. We
> can't get those 16 bits back from the protocol, but we can get them back in
> our implementation'' 
> 
> I will appreciate the comments on it from the reader.
> 
> Thanks
> 
> Likun

The hard part with other classes is that addresses are class specific.
This makes it hard for a cache to work as there isn't any way to
address the nameservers.  Additionally one needs hints or a zone in
a class as a anchor point for the resolver to use as each class has
a independent heirarchy of servers.  That said it wouln't be hard to
define addresses for a new class and have it just work.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka at isc.org