Yes, there’s two approaches I’m using currently. When you register a subdomain you can choose either localhostcert.net or localcert.net. The former has an A record in the public DNS that points to 127.0.0.1. The latter has no public A records so you need to manage them yourself, possibly with a local DNS resolver like unbound.
Why (for what use cases) would one use the former? Browsers solve this by treating localhost as a secure context (i.e. no mixed content warnings etc.) even if you use plain http.
Yes, there’s two approaches I’m using currently. When you register a subdomain you can choose either
localhostcert.netorlocalcert.net. The former has an A record in the public DNS that points to 127.0.0.1. The latter has no public A records so you need to manage them yourself, possibly with a local DNS resolver like unbound.Why (for what use cases) would one use the former? Browsers solve this by treating localhost as a secure context (i.e. no mixed content warnings etc.) even if you use plain http.