starred/dnss
1
0
Fork 0
mirror of https://github.com/albertito/dnss.git synced 2026-04-26 18:05:57 +03:00
Code Issues 5 Projects Releases Packages Wiki Activity

[GH-ISSUE #2] DNSSEC support #2

New issue
Closed
opened 2026-03-02 23:35:52 +03:00 by kerem · 3 comments
kerem commented 2026-03-02 23:35:52 +03:00
Owner
Copy link

Originally created by @alexandrestein on GitHub (Jan 9, 2019).
Original GitHub issue: https://github.com/albertito/dnss/issues/2

Originally assigned to: @alexandrestein on GitHub.

Hi,
thank you for this package it is simple and efficient.

Is there any plan to support DNSSEC?

Originally created by @alexandrestein on GitHub (Jan 9, 2019). Original GitHub issue: https://github.com/albertito/dnss/issues/2 Originally assigned to: @alexandrestein on GitHub. Hi, thank you for this package it is simple and efficient. Is there any plan to support **DNSSEC**?
kerem 2026-03-02 23:35:52 +03:00
kerem commented 2026-03-02 23:35:53 +03:00
Author
Owner
Copy link

@albertito commented on GitHub (Aug 10, 2019):

Hi! Sorry for not responding before, I didn't realize this was still open :(

dnss passes through queries and is quite agnostic to the record types.

For example, in "dns to https" mode, lookups of DNSSEC-enabled domains work fine, and the record types are passed through to the resolvers fine as well.

Is there anything in specific about DNSSEC that isn't working, or any particular mode you'd like to be supported?

<!-- gh-comment-id:520183945 --> @albertito commented on GitHub (Aug 10, 2019): Hi! Sorry for not responding before, I didn't realize this was still open :( dnss passes through queries and is quite agnostic to the record types. For example, in "dns to https" mode, lookups of DNSSEC-enabled domains work fine, and the record types are passed through to the resolvers fine as well. Is there anything in specific about DNSSEC that isn't working, or any particular mode you'd like to be supported?
kerem commented 2026-03-02 23:35:53 +03:00
Author
Owner
Copy link

@alexandrestein commented on GitHub (Aug 11, 2019):

Yes, sorry it wasn't clear.

I would like to have DNSSEC validation directly inside the package.

In the meantime I moved to an other solution.
So I don't need it anymore 🥺

Thanks 😊

<!-- gh-comment-id:520257518 --> @alexandrestein commented on GitHub (Aug 11, 2019): Yes, sorry it wasn't clear. I would like to have DNSSEC validation directly inside the package. In the meantime I moved to an other solution. So I don't need it anymore 🥺 Thanks 😊
kerem commented 2026-03-02 23:35:53 +03:00
Author
Owner
Copy link

@albertito commented on GitHub (Aug 13, 2019):

Ah! I see, thanks for clarifying.

No, no plans for DNSSEC validation in the proxy just yet. I would definitely consider patches (provided they don't increase the complexity significantly), but at the moment don't have plans to actively work on it myself.

Thanks!

<!-- gh-comment-id:521043270 --> @albertito commented on GitHub (Aug 13, 2019): Ah! I see, thanks for clarifying. No, no plans for DNSSEC validation in the proxy just yet. I would definitely consider patches (provided they don't increase the complexity significantly), but at the moment don't have plans to actively work on it myself. Thanks!
kerem changed title from [GH-ISSUE #2] DNSSEC support to [GH-ISSUE #2] DNSSEC support 2026-03-13 21:28:22 +03:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
next
v0.1.0
Labels
Clear labels   
enhancement

   
enhancement

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
wontfix
No labels
enhancement
enhancement
pull-request
question
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dnss#2
No description provided.