dufs VS CoreDNS

Sounds helpful if you're using Apache. I use dufs (https://github.com/sigoden/dufs) as a lightweight file server.

I'm with you on wishing WebDAV continued its rollout. These days there are great low-drama server-side deployments like https://github.com/sigoden/dufs. It's run relative too - you could habe multiple dufs processes serving up different directories in different ways. But for WebDAV, you can't simply mount that on the client side for every OS that's equally low configutaion. For that reason, I really like sshfs as it can be initiated from the client-side without a lot of config (just a mkdir of the mapped dir), and it's OK most time despite it's lack of speed and multi-day uptime. I'm on a chromebook now and it turns out that Samba is the easiest client-side tech to use for remote file systems. DAv should've been uniquitous.

WebDAV: https://github.com/sigoden/dufs - has an easy way of launching, and on the releases tab downloads for multiple CPUs/OSs. The rust exe can just be executed from the cli without installation via package managers (wget and tar xf) are all you need.

I use sigoden/dufs. Very simple file browser that doubles as a basic http server. Supports upload, download and basic file manipulation. I feel it's utterly underrated.

So sorry. It only has one f. https://github.com/sigoden/dufs

dufs miniserve

My solution for public media distribution is Caddy¹ on Scaleway Stardust². 10gb of storage isn't really enough (someday I will write I/O for the 75gb of free object storage), but offers unmetered 100mbps data transfer for $3/month. I setup a proxy through Caddy to dufs³ to upload files.

Anything worth keeping goes on an external HD, buy a bigger one each year and make another copy. I also upload all irreplaceable video to Youtube as private videos; I recently went through and granted a few people access to the ones they wanted to see.

¹https://caddyserver.com

²https://www.scaleway.com/en/stardust-instances

³https://github.com/sigoden/dufs

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