blocky VS CoreDNS

I run multiple blocky instances in a kubernetes cluster. I don't know if it makes sense ... but I'm running kubernetes cluster at home, so making sense is relative ;p

The PI is running a DNS proxy (https://github.com/0xERR0R/blocky) and not much else at the moment.

I switched from pihole to https://github.com/0xERR0R/blocky for internal DNS, and I found it to be a lot easier to use compared to pihole. Setting up DNS entries was as easy as typing a single line in their config.yml, and restarting the service.

You could try using blocky instead of pihole. It's stateless and much more friendly to run.

Link to the Projects' GitHub pages: 1. https://github.com/0xERR0R/blocky [Blocky] 2. https://github.com/AdguardTeam/AdGuardHome [AdguardHome] 3. https://github.com/pi-hole/pi-hole [Pi-hole]

Any specific feature you need from pihole that Blocky doesn't have? Blocky is a much nicer tool for AdBlocking especially if deployed in k8s because it's stateless and configured via a single config file. Plus it's written in Go!

Still, to answer the question: https://github.com/0xERR0R/blocky

There is also blocky. I like it because it is light, declarative, stateless, can use redis as cache and has prometheus integration. This plays really nicely with my setup.

CoreDNS supports this via the bind plugin.

I'd like to use Cloudflare's 1.1.1.1 and 1.0.0.1 nameservers in Kubernetes, alongside DNS over TLS. It looks like I can do it using core-dns. I need to setup the following somehow:

Shamless plug for CoreDNS. Much better DNS server than classic bind9. And of course there's already a nice container image for it.

But another approach that could work in Kubernetes, because the DNS servers are within the cluster itself, would be to work directly with the DNS server pods. In most Kubernetes clusters, whether standalone or managed (GKE, AKS, EKS), the cluster DNS is either coredns or kube-dns. That was great to minimize how much configuration options we’d need to support. We realized we could edit the coredns or kube-dns configmap resources to enable their log option, which would make them log all the queries they handle. We’ll cover exactly how it’s done in more detail below.

CoreDNS has an ectd plugin, so your service could add entries to a database, which is used as record source. Not the same mechanism as you have described, but it will get the job done. Also this is what Kubetnetes does for incluster dns records.

nevermind there's caddy builtin upgrade method https://github.com/coredns/coredns/issues/6034

Coredns can be spun up in a docker container, just starting to get into it myself

CoreDNS is a pretty good DNS server.

Core DNS (https://coredns.io).