Who benefits from this? Even though Let’s Encrypt stresses that most site operators will do fine sticking with ordinary domain certificates, there are still scenarios where a numeric identifier is the only practical choice:
Infrastructure services such as DNS-over-HTTPS (DoH) – where clients may pin a literal IP address for performance or censorship-evasion reasons.
IoT and home-lab devices – think network-attached storage boxes, for example, living behind static WAN addresses.
Ephemeral cloud workloads – short-lived back-end servers that spin up with public IPs faster than DNS records can propagate.
I use a domain, but for homelab I eventually switched to my own internal CA.
Instead of having to do
service.domain.tld
it’s nice to doservice.lan
.Any good instructions you would recommend for doing this?
use the official home.arpa as specified in RFC 8375