CoreDNS VS alternate

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).

The best response I got was from the coredns slack channel with the suggestion to use the alternate plugin. However, as I stated in this post, I have no success with a build.

I asked the same question in the coredns slack channel: https://cloud-native.slack.com/archives/C4DF7FP71/p1666749213748099?thread_ts=1666749213.748099&cid=C4DF7FP71. The suggestion was to use the alternate plugin. At the time of this writing, I have not been able to complete a custom build of coredns which includes the plugin.