Friendly names for private services using Headscale, CoreDNS and DNSimple

When I started setting up private, self-hosted services one of the things I wanted to maintain was a pattern of friendly, human readable names to access them. I didn't want the overhead of bookmarking domains available via Tailscale's MagicDNS and I wanted real SSL certificates that were trusted and that clients wouldn't complain about. The tools To accomplish this, I have DNSimple managing the public zone (for things like this site, my Mastodon instance and so forth). I have Headscale set up as the control plane and I use Tailscale's apps to connect to it. It assigns addresses to each node, dictates what each node can reach and which resolver each uses for a given domain. I'm using CoreDNS to map friendly names to mesh addresses: coryd.dev { cache 300 hosts { 100.xx.xx.xx music.coryd.dev 100.xx.xx.xx books.coryd.dev 100.xx.xx.xx photos.coryd.dev 100.xx.xx.xx git.coryd.dev fallthrough } forward . 45.90.28.0 1.1.1.1 log errors } fallthrough allows anything not defined above it in the…