
How many instances are you running. Having a single point of failure seems risky to me

How many instances are you running. Having a single point of failure seems risky to me

Someone could steal your root

Why though?
It was pushed as a standard after .lan was in use

.lan exists and has the advantage of not being taken

I would recommend DNS verification instead
You can setup a single device to pull the cert and then use a script to automatically copy it to the destination via SSH

Why use Traefik? You could just put a reverse proxy on each device and then automate it all with a simple script

Self signed also makes it easy for someone to compromise https on your network
If you need to use a self sign certificate make sure to add name restrictions in the root so that it can’t be used for public domains

Just use .lan
It is way simpler and has been in use long before .home.arpa

RFC 8375 is such a joke
Using lan is the standard even if the standards bodies refuse to recognize it. Even openwrt uses it and they typically adhere to the RFC

Don’t use TLS with local domains like lan. It is fairly risky and prone to issues.
They are fine for ssh and other services not dependent on TLS though
You don’t need that many VMs. For networking get a dedicated box (can be a used consumer device) and then create a few VMs to run podman containers.
If you do want a dedicated instance for a service use LXC
Except that isn’t really a fair comparison. Private ranges aren’t any more complicated than public ranges so it doesn’t impact me when using IPv4 private IPs.
.home.arpa is one of the most “designed by committee” domains I have heard in my life. It is way longer than .lan and defeats the point of local domains to begin with. I might as well use a public domain instead. .lan was around long before the standard and will be around long after
If .lan becomes a TLD (it won’t) I can always go though and change it to something like lan1 or .mylan both of which would be shorter and easier to type