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.

Sign up for GitHub

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

Jump to bottom

Feature request: DNS over HTTPS in Go to replace Unbound #137

Open
qdm12 opened this issue Apr 12, 2020 · 7 comments · May be fixed by #1742
Open

Feature request: DNS over HTTPS in Go to replace Unbound #137

qdm12 opened this issue Apr 12, 2020 · 7 comments · May be fixed by #1742
Assignees
@qdm12
Labels
Category: DNS 📠
Projects
Development

Comments

@qdm12
Copy link
Owner

qdm12 commented Apr 12, 2020 •
edited

We should adopt https://github.com/qdm12/dns/releases/tag/v2.0.0-rc5 even if it has no DNSSEC validation builtin yet. Main reason being most domains are not DNSSEC secured, and so your DNS provider (cloudflare, google etc.) can lie about the records for these unsecured domains, even if you can securely proof these are unsecured. So not really a point so much, although this will be done (see qdm12/dns#97)

This is blocked by an upgrade of the qdm12/gosettings library to v0.4.0-rc9
@qdm12 qdm12 self-assigned this Apr 12, 2020
@qdm12 qdm12 added this to To do in Development via automation Apr 12, 2020
@qdm12 qdm12 moved this from To do to In progress in Development Jul 26, 2020
@qdm12 qdm12 moved this from In progress to To do in Development Aug 27, 2020
@qdm12 qdm12 mentioned this issue Nov 4, 2020
Open
4 tasks
This was referenced Mar 9, 2021
Closed
Closed
@qdm12 qdm12 moved this from To do to In progress in Development Apr 9, 2021
This was referenced Jan 22, 2022
Closed
Closed
Open
@qdm12 qdm12 mentioned this issue Mar 13, 2022
Closed
@denizdogan
Copy link

I just wanted to check in on the progress here! Are we there yet? 😄

@qdm12
Copy link
Owner Author

qdm12 commented Jun 11, 2022

It's still a work in progress at https://github.com/qdm12/dns/tree/v2.0.0-beta I can't give an exact timeline, but it's almost done.

@qdm12 qdm12 mentioned this issue Jun 12, 2022
Closed
@jcheroske
Copy link

It would be great if a specific DoT server could be specified, and not just providers. Not sure if this is doable now, but I haven't been able to find it.

@qdm12 qdm12 mentioned this issue Sep 9, 2022
Closed
@qdm12 qdm12 mentioned this issue Oct 17, 2022
Open
@leo15dev leo15dev mentioned this issue Nov 17, 2022
Open
@qdm12 qdm12 mentioned this issue Apr 3, 2023
Open
@frepke
Copy link
Collaborator

frepke commented Apr 30, 2023

It's still a work in progress at https://github.com/qdm12/dns/tree/v2.0.0-beta I can't give an exact timeline, but it's almost done.

Hi Quentin, any information available?
And can we expect an implementation in Gluetun when it's ready?

@qdm12
Copy link
Owner Author

qdm12 commented Jul 11, 2023

Can anyone try image qmcgaw/gluetun:pr-1742? It uses DNS over TLS in Go which I wrote with my own lil' fingers (arguably better than dns over https). Options should all be the same as before. The main difference is it doesn't do DNSSEC validation, which, after a lot of digging, turns out to be not that useful. I'll work on it though, but it doesn't feel like a blocking priority to drop Unbound.

This will allow a lot more options and customizations (even Prometheus metrics at some point, it's already in the dns server Go code).

@qdm12 qdm12 linked a pull request Jul 11, 2023 that will close this issue
Open
@qdm12 qdm12 mentioned this issue Aug 7, 2023
Closed
This was referenced Sep 15, 2023
Closed
Open
@qdm12 qdm12 mentioned this issue Sep 24, 2023
Open
@pduchnovsky
Copy link

pduchnovsky commented Jan 6, 2024 •
edited

Can anyone try image qmcgaw/gluetun:pr-1742? It uses DNS over TLS in Go which I wrote with my own lil' fingers (arguably better than dns over https). Options should all be the same as before. The main difference is it doesn't do DNSSEC validation, which, after a lot of digging, turns out to be not that useful. I'll work on it though, but it doesn't feel like a blocking priority to drop Unbound.

This will allow a lot more options and customizations (even Prometheus metrics at some point, it's already in the dns server Go code).

What needs to be tested exactly ?
Also, how safe is it to test this version in 'production' at this stage ? :D
Also, this would bring no improvement for people using DOT=off with DNS_PLAINTEXT_ADDRESS= right.
I am experiencing huge spikes in memory usage even with these settings so I was looking for a solution, even with 1500 mem limits gluetun reaches max memory and gets killed off, breaking remaining connections etc.. :/
This is with 50MB/s usage.

This was referenced Mar 20, 2024
Open
Open
Closed
@gaby
Copy link

gaby commented Mar 27, 2024

@qdm12 Why not use CoreDNS? That way people can use their CoreFile and also get access to all the functionality of CoreDNS. It's based in Go

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@qdm12 qdm12

Labels
Category: DNS 📠
Projects
Development
  
In progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(dns): use qdm12/[email protected] qdm12/gluetun
6 participants
@denizdogan @gaby @jcheroske @frepke @qdm12 @pduchnovsky