nimforum VS CoreDNS

If the video example does not work, you can use the examples projects in the nim SDL repository. When ex101_init.nim works, there is no reason the video example does not work. If you have further issues, do not hesitate to share a minimal working example with your detailed configuration (Nim compiler version, command line you used, file directory, libraries installed) on the forum.nim-lang.org

It might be worth posting this on the official nim forum (https://forum.nim-lang.org/) to cast a wider net.

Obviously forums aren't as popular as they used to be, so this topic might not be of interest to many. For folks that want to run a forum, they'd most certainly go with Discourse (Ruby), Flarum (PHP), Xenforo (PHP), NodeBB (Javascript), Nimforum (Nim) and maybe Casnode (Go)

https://forum.nim-lang.org/ doesn't let me post.

NimForum - https://github.com/nim-lang/nimforum

You sound like you are in just the right demographic to love Nim...The Forum [1] is a good place to get support.

https://forum.nim-lang.org/

"embedded" can mean a few different things so that's a bit confusing for me, but if the intent was "show me places sqlite is used as a database backend for user-facing web software", the Nim forum (https://github.com/nim-lang/nimforum) uses sqlite as its database backend.

I love NimForum, like a simplified discourse and super light on resources. Example

https://forum.nim-lang.org

uses sqlite, is actively improved, they claim the nim language makes small cross-platform binaries but none for this release it seems.

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