Alternatives
Products that do what SecondDNS does
Automatic secondary DNS — zone sync, failover
- 1NI
2019 · nextdns.io
- 2WD
2020 · which.nameserve.rs
- 3GD
2017 · github.com
- 4DA
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
- 5IB
I built a DNS resolver that lets me use https://frontend.numa instead of localhost:5173 — auto-generated TLS certs, WebSocket passthrough, path routing. No mkcert, no nginx, no /etc/hosts.
Apr 2026 · github.com
- 6OT
After the major outages from AWS and Cloudflare, I began wondering how to make my own services more resilient. Using nameservers from different providers is doable but a bit tricky to manage. OctoDNS helps automate keeping the zones synced so AWS, Cloudflare, etc. are all serving the same information. In an age of centralized infrastructure, we can exploit the capabilities from the origins of the decentralized internet.
Nov 2025 · octodns.readthedocs.io
- 7
- 8KE
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
- 9GB
2014 · dns-api.com
- 10QA
2022 · github.com
- 11SD
Most site blockers work by blacklisting distractions. That never worked for me, the internet is too big, and there’s always something new to waste time on. I wanted the opposite: allowlist‑only browsing. Block everything by default, and explicitly allow only what I need. So I built Sinkzone: a local DNS forwarder with two modes: Monitor mode: lets all traffic through, but logs every domain so you can decide what to allow. Focus mode: only allowlisted domains resolve; everything else is blocked (NXDOMAIN). It’s open source, written in Go, and runs locally on macOS, Linux, and Windows. Works a…
2025 · github.com
- 12RT
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
- 13IB
Hey everyone. It's Sherub here, author of the Build your own DNS Server challenge on CodeCrafters. Currently it’s available in Rust, Go, and Python and is free while in beta. https://codecrafters.io/dns-server I've kept the challenge accessible but still challenging for an intermediate developer. This challenge, like others from CodeCrafters, is self-paced. You can use any tools you prefer (terminal, editor, etc.) to build the project. At the end of the challenge, you will have created a DNS forwarding server. The server can create and read DNS packets and respond to DNS…
2023 · app.codecrafters.io
- 14ED
2014 · slimdns.com
- 15SD
2015 · github.com
- 16FD
2023 · eighty-twenty.org
- 17IT
2013 · 5f5.org
- 18AS
2014 · dhcp.io
- 19DD
2013 · samarudge.github.io
- 20DB
I built a CLI to benchmark DNS resolvers after discovering DNS was adding 300ms to my API requests. v0.3.0 just released with new features: compare: Test single domain across all resolvers top: Rank resolvers by latency/reliability/balanced monitor: Continuous tracking with threshold alerts 1,400+ downloads in first week. Quick start: pip install dns-benchmark-tool dns-benchmark compare --domain google.com CLI stays free forever. Hosted version (multi-region, historical tracking, alerts) coming Q1 2026. GitHub: https://github.com/frankovo/dns-benchmark-tool…
Nov 2025 · github.com
- 21AO
If my experience is any indicator, the DNS issue seems to be getting worse as the hours go by, not better. However, I have found that adding OpenDNS servers (208.67.222.222, 208.67.222.222) to my list of DNS servers has completely eliminated the issue, at least for the time being. So, under my IPv4 configuration, in the "DNS Servers" field, I have "208.67.222.222, 208.67.222.222, 8.8.8.8" - the last one is the Google DNS server. I'm able to resolve Twitter, Github, etc.
2016
- 22BI
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
- 23
- 24OD
Hey HN! We built DNS Directory (https://dnsdirectory.com), a free, searchable database of public DNS servers with live monitoring every 10 minutes. We needed to find an up-to-date list of DNS servers used by carriers around the world for a proxy fingerprinting / web-scraping project but we were shocked to find that it didn’t exist so we built it ourselves in an internal Hackathon We’re adding more features but so far we: Test 77K+ servers every ~10 minutes Allow filtering by uptime, location, security features (ad blocking, malware protection, DNSSEC) Show info on IPv6…
Dec 2025 · dnsdirectory.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →