tomsawyer126 at gmail.com
Fri Aug 15 02:57:05 UTC 2014
Hi, Evan and all.
I have did some trick to modify the current rbtdb cache database to support
client-subnet, but it's unstable. Because I haven't familiar with all of
BIND features and how it does , so frequently I will ignore some case which
will finally cause big problem. So ,I suppose I stuck into a infinite
My idea is simple, base on the current rbtdb whose node has a data pointer
directly point to rdatasetheader_t , I want to make the data pointer point
to a isc_radix_tree and for each radix_node indicating a client-subnet has
a pointer points to rdatasetheader_t. Then ,when a request is received and
recursive query is required , we try to parse the edns-client-subnet option
and use it as a parameter when create new fetchctx. Is this a possible
If not, please show me why there's a must of rewriting the cache database,
and do you have any ideas how it will looks like , I have huge interest of
try to implement it, thank you.
On Sun, Jun 29, 2014 at 7:44 AM, Evan Hunt <each at isc.org> wrote:
> On Tue, Jun 24, 2014 at 03:14:35PM +0800, Tom Sawyer wrote:
> > When I look through the source code of bind-9.9.5 I find fromwire_opt()
> > function in lib/dns/rdata/generic/opt_41.c , which include a case about
> > parsing DNS_OPT_CLIENT_SUBNET option. Is this indicating that bind will
> > support EDNS-CLIENT-SUBNET recursive query soon?
> We're open to it, but it probably won't happen unless someone
> contributes the code to us, or sponsors the feature financially so we
> can hire an engineer. It's an enormous job of work (requiring a major
> rewrite of the cache database), and we have our hands full as it is.
> Evan Hunt -- each at isc.org
> Internet Systems Consortium, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the bind-workers