[GH-ISSUE #138] Improvement suggestion: DNS over HTTPS #54

Closed
opened 2026-02-26 04:33:54 +03:00 by kerem · 5 comments
Owner

Originally created by @noglitchyo on GitHub (May 23, 2019).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/138

Hello,

First of all, thanks for your work on dns-proxy-server. You made there an amazing tool, which ease my work in many ways :)

I would like to suggest an improvement for it.

What do you think about the idea of implementing DNS over HTTPS protocol into dns-proxy-server?
Please have a look at: https://tools.ietf.org/html/rfc8484

I think it could greatly increase portability for dns-proxy-server and ease its configuration.
Especially on Windows system since browsers start to implement this feature.
This would be really useful when network configuration update is restricted on the system and only the browser configuration can be changed.

Let me know what you think.

Originally created by @noglitchyo on GitHub (May 23, 2019). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/138 Hello, First of all, thanks for your work on dns-proxy-server. You made there an amazing tool, which ease my work in many ways :) I would like to suggest an improvement for it. What do you think about the idea of implementing DNS over HTTPS protocol into dns-proxy-server? Please have a look at: https://tools.ietf.org/html/rfc8484 I think it could greatly increase portability for dns-proxy-server and ease its configuration. Especially on Windows system since browsers start to implement this feature. This would be really useful when network configuration update is restricted on the system and only the browser configuration can be changed. Let me know what you think.
kerem 2026-02-26 04:33:54 +03:00
  • closed this issue
  • added the
    feature
    label
Author
Owner

@mageddo commented on GitHub (Jun 6, 2019):

@noglitchyo thanks for the suggestion

At the first place this idea looks great to me

  1. I will have to study this feature to understand it's idea better
  2. DPS DNS server is based on https://github.com/miekg/dns I will have to check if I would be able to use that or if I will have to implement the HTTP API
  3. After all I will have to measure how big is the change to be fully implemented

Regards

<!-- gh-comment-id:499326996 --> @mageddo commented on GitHub (Jun 6, 2019): @noglitchyo thanks for the suggestion At the first place this idea looks great to me 1. I will have to study this feature to understand it's idea better 2. DPS DNS server is based on https://github.com/miekg/dns I will have to check if I would be able to use that or if I will have to implement the HTTP API 3. After all I will have to measure how big is the change to be fully implemented Regards
Author
Owner

@noglitchyo commented on GitHub (Jun 6, 2019):

@mageddo Thank you for your reply.

I will have to check if I would be able to use that or if I will have to implement the HTTP API

I made some researches on the repository you mentionned.
Seems that some attempts to implement DoH (client) in the library were made and then reverted:

semihalev/dns which is also based on miekg/dns actually made a DoH server implementation (if you want to have a look) and had to implement the HTTP API.

<!-- gh-comment-id:499378344 --> @noglitchyo commented on GitHub (Jun 6, 2019): @mageddo Thank you for your reply. > I will have to check if I would be able to use that or if I will have to implement the HTTP API I made some researches on the repository you mentionned. Seems that some attempts to implement DoH (client) in the library were made and then reverted: - https://github.com/miekg/dns/pull/649 - https://github.com/miekg/dns/pull/651 - https://github.com/miekg/dns/pull/671 - https://github.com/miekg/dns/pull/800 [semihalev/dns](https://github.com/semihalev/sdns) which is also based on [miekg/dns](https://github.com/miekg/dns ) actually made a [DoH server implementation](https://github.com/semihalev/sdns/blob/master/doh/doh.go) (if you want to have a look) and had to implement the HTTP API.
Author
Owner

@webaaz commented on GitHub (May 6, 2021):

Is there any update?

<!-- gh-comment-id:833561878 --> @webaaz commented on GitHub (May 6, 2021): Is there any update?
Author
Owner

@mageddo commented on GitHub (Dec 25, 2025):

Alpha is out since 5.7.x. I would appreciate feedback.

Looks like DNS Over HTTPS was not designed for development, but for production use with high security constraints. For this reason I found some caveats and put them on that draft, needs work to improve the docs.

Docs

<!-- gh-comment-id:3691827734 --> @mageddo commented on GitHub (Dec 25, 2025): Alpha is out since [5.7.x][1]. I would appreciate feedback. Looks like DNS Over HTTPS was not designed for development, but for production use with high security constraints. For this reason I found some caveats and put them on [that draft][3], needs work to improve the docs. Docs * [Activation][2] * [Configurations][3] [1]: https://github.com/mageddo/dns-proxy-server/releases [2]: https://github.com/mageddo/dns-proxy-server/blob/cdabe7b/docs/content/3-configuration/_index.en.md#doh-server [3]: https://github.com/mageddo/dns-proxy-server/tree/cbc7a5f/doh
Author
Owner

@mageddo commented on GitHub (Dec 26, 2025):

Made some improvements at 5.8.3 and created the docs. I consider it beta now.

<!-- gh-comment-id:3693455893 --> @mageddo commented on GitHub (Dec 26, 2025): Made some improvements at 5.8.3 and created the [docs][1]. I consider it beta now. [1]: http://mageddo.github.io/dns-proxy-server/latest/en/2-features/doh/
Sign in to join this conversation.
No milestone
No project
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/dns-proxy-server-mageddo#54
No description provided.