Alternatives
Products that do what LHDNS does
A privacy-preserving naming layer for the internet
- 1
- 2DA
Tired of companies snooping through your DNS traffic? Don't you wish you could get advertisements with your DNS records? Today we're introducing the innovative, privacy-focused, ad-supported DNS resolver - DN$! Traditional DNS resolvers provided by your internet service provider, cloudflare, or google could be tracking your internet activity and selling it to third-party data vendors. We at DN$ want to fix that and cut out these nefarious actors (until we've amassed a critical number of users to exploit). In order to support such a radically new business model, our service needs to serve…
2024 · github.com
- 3PD
2024 · privacy-dns.pw
- 4NI
2019 · nextdns.io
- 5NA
We just shipped a new feature in NextDNS: Bypass Age Verification. More and more sites (especially adult ones) are now forcing users to upload IDs or selfies to continue. We think that’s a terrible idea: handing over government documents to random sites is a huge privacy risk. This new setting workarounds those verification flows via DNS tricks. It’s available today to all users, including free accounts. We’re curious how the HN community feels about this. Is it the right way to protect privacy online, or will it just provoke regulators to push harder? https://nextdns.io
2025
- 6RT
Every privacy-focused DNS service requires an account: NextDNS, Cloudflare for Families, Apple's iCloud Private Relay (paid, iOS-only). The protocol that doesn’t require one - ODoH - had basically one well-known public relay operator (Frank Denis on Fastly Compute, default in dnscrypt-proxy). I built a second one and the client to talk to it.
May 2026 · numa.rs
- 7EB
2017 · github.com
- 8
- 9
- 10
- 11
- 12QA
2022 · github.com
- 13SS
2019 · github.com
- 14
- 15
- 16FD
2023 · eighty-twenty.org
- 17BI
I was setting up tests involving DNS resolution recently, where something like 127.0.0.1.service.foo would have been tremendously useful. Back in the day, I'd have used xip.io - but sadly that service died. Well, every excuse is a good one when it comes to writing a DNS server! Backname.io joins nip.io and sslip.io in the wildcard DNS game.
2023 · backname.io
- 18LD
Hi HN! I'm Jarek, and I've built this tool that allows publishing .local domains on the local network using mDNS. It also has a reverse proxy that handles HTTPS termination and port forwarding. I'm working on adding more features, like an index page with all available domains or allowing proxy redirects, so you could redirect from HTTP to HTTPS. Let me know if you have any questions or feedback!
2023 · localcan.com
- 19SA
2021 · sirendns.com
- 20
- 21KE
My goal was to create a DNS server as simple as the LDAP server I've been contributing to (glauth) and here it is: https://github.com/fusion/kittendns A few things to know about it: - It is easy to configure using a Toml file - I am using it to bail my coredns/etcd instances when under attack - (yes, it also works as a service location server) - It comes with a simple, plain English, rule engine that doesn't do much at this point - It can be used with LetsEncrypt. I use it to retrieve certificates for my home servers. - RFC: all the nice ones :) Anyway, feedback is…
2022
- 22
- 23
- 24AA
We launched an API for custom hostnames today. A simple HTTP post with a hostname gets a temp hostname with CNAME/a record instructions, as soon as DNS is setup we issue SSL and start accepting traffic for that hostname. It's the quickest way we know of to provision custom hostnames: https://fly.io/mix/custom-hostnames/ When we started building Fly, we figured it was too late to "make SSL easy and the customers will come". Lets Encrypt changed the world, and we knew many companies rolling their own SSL support with nginx, Traefik, etc, etc. It seemed like a…
2017
Ranked by how close each launch is in meaning, then by votes. Refine with a description →