Skip to content
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

Closed
gmadkat opened this issue Oct 7, 2014 · 10 comments
Closed

C and nodejs sample code for edns-client-subnet #72

gmadkat opened this issue Oct 7, 2014 · 10 comments

Comments

@gmadkat
Copy link
Contributor

gmadkat commented Oct 7, 2014

No description provided.

@amankin
Copy link

amankin commented Oct 7, 2014

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.

@amankin amankin changed the title Add EDNS support Enhanced EDNS0, including reflecting it in the README! Oct 7, 2014
@wtoorop wtoorop changed the title Enhanced EDNS0, including reflecting it in the README! C and nodejs sample code for edns-client-subnet Oct 27, 2014
@wtoorop
Copy link
Contributor

wtoorop commented Oct 27, 2014

I've updated the README. Only thing left now is the sample code.

@ngoyal
Copy link
Contributor

ngoyal commented Oct 27, 2014

Node support is in the getdns-1.5 branch of the node bindings repo.

@amankin
Copy link

amankin commented Oct 27, 2014

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.


Reply to this email directly or view it on GitHubhttps://github.com//issues/72#issuecomment-60593321.

@wtoorop
Copy link
Contributor

wtoorop commented Oct 28, 2014

Op 27-10-14 om 22:33 schreef Allison Mankin:

Willem

Will the web site point to the new spec?

Yes.

@wtoorop
Copy link
Contributor

wtoorop commented Oct 28, 2014

That is: Our website will show the adapted spec at
https://getdnsapi.net/spec/ .

Hopefully Paul's website will reference or redirect to that location
then as well.

Op 28-10-14 om 11:11 schreef Willem Toorop:

Op 27-10-14 om 22:33 schreef Allison Mankin:

Willem

Will the web site point to the new spec?

Yes.

@amankin
Copy link

amankin commented Oct 28, 2014

That is what Paul said in his mail to us, and I wrote him and said thank you, we’d like that.
On Oct 28, 2014, at 3:12 AM, wtoorop <notifications@github.commailto:notifications@github.com> wrote:

That is: Our website will show the adapted spec at
https://getdnsapi.net/spec/ .

Hopefully Paul's website will reference or redirect to that location
then as well.

Op 28-10-14 om 11:11 schreef Willem Toorop:

Op 27-10-14 om 22:33 schreef Allison Mankin:

Willem

Will the web site point to the new spec?

Yes.


Reply to this email directly or view it on GitHubhttps://github.com//issues/72#issuecomment-60733705.

@saradickinson
Copy link
Contributor

@wtoorop Can this issue be closed?

@wtoorop
Copy link
Contributor

wtoorop commented Apr 19, 2017 via email

johndickinson pushed a commit to johndickinson/getdns that referenced this issue Jan 11, 2019
Add output of basic config to the logs to aid debugging.
@wtoorop
Copy link
Contributor

wtoorop commented Feb 20, 2020

Well at least we now have the edns_client_subnet_private setting, so closing...

@wtoorop wtoorop closed this as completed Feb 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants