My home DNS is a bit of a mess, so I want to install CoreDNS on my Synology NAS to tidy it all up. I’ll run it in a container.

While debugging pod DNS problems, I discovered that CoreDNS allows customization by importing extra zone files from a config map. I’m going to use that to forward queries for k3s.differentpla.net to my custom CoreDNS instance.

I’ve got an extra instance of CoreDNS running in my cluster, serving *.k3s.differentpla.net, with LoadBalancer and Ingress names registered in it, and it’s working fine for queries to the cluster. It’s not working fine for queries inside the cluster. What’s up with that?

I recently left my k3s cluster turned off for a week or so. When I turned it back on, the k3s.differentpla.net DNS wasn’t working. Let’s figure it out and maybe write a runbook for the next time.

I’m still on the hunt for a way to connect Erlang nodes in a Kubernetes cluster by using pod names.

I’d like to be able to access my load-balanced services by name (docker.k3s.differentpla.net, for example) from outside my k3s cluster. I’m using --addn-hosts on dnsmasq on my router. This is fragile. Every time I want to add a load-balanced service, I need to edit the additional hosts file on my router, and I need to restart dnsmasq.