-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C and nodejs sample code for edns-client-subnet #72
Comments
EDNS0 is supported already for the buffer size info. In the upcoming release, there is support for other uses of EDNS0 because OPT is now available to the interface - this can be used for edns-client-subnet support and we should include sample code for this in C and (by request of a party) node.js. |
I've updated the README. Only thing left now is the sample code. |
Node support is in the getdns-1.5 branch of the node bindings repo. |
Willem Will the web site point to the new spec? On Oct 27, 2014, at 6:41, "wtoorop" <notifications@github.commailto:notifications@github.com> wrote: I've updated the README. Only thing left now is the sample code. — |
Op 27-10-14 om 22:33 schreef Allison Mankin:
Yes. |
That is: Our website will show the adapted spec at Hopefully Paul's website will reference or redirect to that location Op 28-10-14 om 11:11 schreef Willem Toorop:
|
That is what Paul said in his mail to us, and I wrote him and said thank you, we’d like that. That is: Our website will show the adapted spec at Hopefully Paul's website will reference or redirect to that location Op 28-10-14 om 11:11 schreef Willem Toorop:
— |
@wtoorop Can this issue be closed? |
Op 19-04-17 om 14:26 schreef saradickinson:
@wtoorop <https://github.com/wtoorop> Can this issue be closed?
@saradickinson I don't know. @amankin requested the example code.
@amankin do you still want this example?
|
Add output of basic config to the logs to aid debugging.
Well at least we now have the edns_client_subnet_private setting, so closing... |
No description provided.
The text was updated successfully, but these errors were encountered: