dns-over-tls-forwarder
aardvark-dns
Our great sponsors
| dns-over-tls-forwarder | aardvark-dns | |
|---|---|---|
| 1 | 3 | |
| 45 | 155 | |
| - | 7.1% | |
| 6.0 | 8.6 | |
| 11 days ago | 5 days ago | |
| Go | Rust | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
dns-over-tls-forwarder
-
Set up Pi-hole with your own recursive DNS server using DNSSEC
On the choice of DNS forwarder: Unbound is very configurable and reliable. I went down this rabbit hole recently and decided I wanted a DNS "shotgunner" as latency to a single upstream source had a wide distribution.
Simply, you issue multiple DNS requests and take the fastest one. I use 9 different DNS servers over TLS. This is a bit excessive, two is enough most of the time.
I'm tempted to write my own DNS forwarder but this project is working well for me: https://github.com/mikispag/dns-over-tls-forwarder
aardvark-dns
-
Podman v4.4, Buildah v1.29 released!
But wait! There’s more. This week both netavark and aardvark-dns released version 1.5.0. Netavark now includes support for IPVLAN. And aardvark-dns was rebuilt with updated libraries at the very heart of its primary functionality.
-
Issue with internal DNS lookup using nginx proxy manager and podman
It would appear this is a known issue with the new networking stack
-
Podman v4.0 has been released!
Podman now features support for a new network stack based on Netavark and Aardvark, in addition to the existing CNI stack. The new stack features improved support for containers in multiple networks, improved IPv6 support, and improved performance. To ensure that we don’t break existing users, the old CNI stack will remain the default on existing installations, while new installs will use Netavark. We’re planning an in-depth dive into the networking changes in a future blog, so look forward to more details there!
What are some alternatives?
sdns - A high-performance, recursive DNS resolver server with DNSSEC support, focused on preserving privacy.
netavark - Container network stack
mosdns - 一个 DNS 转发器
podman - Podman: A tool for managing OCI containers and pods.
dnsproxy - Simple DNS proxy with DoH, DoT, DoQ and DNSCrypt support
CoreDNS - CoreDNS is a DNS server that chains plugins
dns - Docker DNS server on steroids to access DNS-over-TLS from Cloudflare, Google, Quad9, Quadrant or CleanBrowsing
Pi-hole - A black hole for Internet advertisements
AdGuardHome - Network-wide ads & trackers blocking DNS server
hickory-dns - A Rust based DNS client, server, and resolver
buildah - A tool that facilitates building OCI images.
trust-dns - A Rust based DNS client, server, and resolver [Moved to: https://github.com/hickory-dns/hickory-dns]