-
Updated
Jul 3, 2020 - Go
dns-over-https
Here are 137 public repositories matching this topic...
-
Updated
May 10, 2020 - C
-
Updated
Apr 19, 2020 - Go
-
Updated
Jun 28, 2020 - Go
-
Updated
Jul 6, 2020 - C#
-
Updated
Jun 29, 2020 - Go
-
Updated
May 17, 2020 - Go
Its really nice how you link to the docker prerequisites.
Do you think you could link to tutorials for DNAT, or a specific typical example of the goal setup? Is it just "get your router to forward external UDP requests to the particular machine running this behind the NAT"? Or more complicated because of the docker setup?
-
Updated
Jun 22, 2020 - Go
-
Updated
Jun 27, 2020 - Python
-
Updated
May 13, 2020 - C
-
Updated
Jun 19, 2020 - HTML
-
Updated
May 27, 2020 - Go
-
Updated
Jul 5, 2020 - Go
-
Updated
Jul 4, 2020 - Dockerfile
-
Updated
Feb 29, 2020
-
Updated
Jul 6, 2020 - C#
-
Updated
Aug 11, 2019 - Python
-
Updated
Dec 5, 2019
-
Updated
Jun 10, 2020 - Go
-
Updated
Dec 15, 2016 - Objective-C
-
Updated
Jun 12, 2020 - Shell
Add example code and documentation for using different web frameworks. Also add enhanced support as appropriate (e.g. type hints) per framework.
Some frameworks we could focus on
- Angular
- React
- Vue
Improve this page
Add a description, image, and links to the dns-over-https topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the dns-over-https topic, visit your repo's landing page and select "manage topics."



It wasn't documented or obvious (to me at least) that for
nextdnsto work after install I needed to remove any system name servers (System -> Name Server section in EdgeOS web UI). I had the NextDNS name servers added there, so my network resolved DNS correctly, but only a small percentage was using secure DNS. Removing the system name servers (and resetting NextDNS logs) resulted in 100% secure