HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
tssva
dnshttps-proxy
HISTORICAL RECORD2016–2016
tssva / dnshttps-proxy · Not publicly available

dnshttps-proxy

Discover this repository through its Hacker News conversations.

2Distinct people
2Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2016-09-30 13:40:32 UTC to 2016-09-30 18:05:58 UTC.

012016-09-30 13:00:00 UTC to 2016-09-30 14:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 30, 13:002016-09-30 14:00:00 UTC to 2016-09-30 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-09-30 15:00:00 UTC to 2016-09-30 16:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 30, 15:002016-09-30 16:00:00 UTC to 2016-09-30 17:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-09-30 17:00:00 UTC to 2016-09-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-09-30 18:00:00 UTC to 2016-09-30 19:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 30, 18:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 30, 13:002016-09-30 13:00:00 UTC2016-09-30 14:00:00 UTC101
Sep 30, 14:002016-09-30 14:00:00 UTC2016-09-30 15:00:00 UTC000
Sep 30, 15:002016-09-30 15:00:00 UTC2016-09-30 16:00:00 UTC000
Sep 30, 16:002016-09-30 16:00:00 UTC2016-09-30 17:00:00 UTC000
Sep 30, 17:002016-09-30 17:00:00 UTC2016-09-30 18:00:00 UTC000
Sep 30, 18:002016-09-30 18:00:00 UTC2016-09-30 19:00:00 UTC101

What Hacker News says

2 sources
There are several different implementations of proxies for DNS-over-HTTPS: https://github.com/aarond10/https_dns_proxy (C) https://github.com/pforemski/dingo (Golang) https://github.com/tssva/dnshttps-proxy (Golang) https://github.com/wrouesnel/dns-over-https-proxy (Golang) https://github.com/CodeFalling/dns-proxy-https (Javascript) I'd heard that somebody was working on DNS-over-HTTPS support for https://github.com/getdnsapi/getdns at the hackathon in Buenos Aires in April just before DNS-OARC / IETF-95, but have seen no evidence of that.
In DNS-over-HTTPS
I didn't mention it in my original comment because I thought the code didn't exist anymore but I found an old Time Machine backup disk with the code on it for an updated version of the referenced implementation. I have put it up on Github at https://github.com/tssva/dnshttps-proxy. I need to throw up a README and give attribution. Will get to that later today. This version will support all RR types supported by the miekg/dns library which is the vast majority of them and any you are likely to come across in the wild. It also allows you to specify regular DNS resolvers which can be used in two ways. As fallback if connectivity to the DNS over HTTPS service fails or to always use to resolve specific domains. It also allows you to restrict access to the proxy to certain networks. The rest of the code should be IPv6 friendly but for some reas
Read the rest
on I implemented the access list in a manner that only supports specifying IPv4 networks. Guess I have something to work on. If no DNS resolvers are specified it attempts to use the Google Public DNS servers to resolve dns.google.com. If DNS resolvers are specified they are used to resolve dns.google.com. A flag to always use the Google Public DNS servers would be useful, so now I have 2 things to work on. As far as performance impact I have generally seen from 20 - 80msec of additional delay. Using a caching resolver behind the proxy would help mitigate this. As is the additional delay is pretty much unnoticeable when web browsing.
In DNS-over-HTTPS

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.