use the official home.arpa as specified in RFC 8375
Comment on Let’s Encrypt Begins Supporting IP Address Certificates
martin@lemmy.caliban.io 3 months agoAny good instructions you would recommend for doing this?
eneff@discuss.tchncs.de 3 months ago
fmstrat@lemmy.nowsci.com 3 months ago
No thanks. I get some people agreed to this, but I’m going to continue to use
.lan, like so many others. If they ever register.lanfor public use, there will be a lot of people pissed off.IMO, the only reason not to assign a top-level domain in the RFC is so that some company can make money on it. The authors were from Cisco and Nominum, a DNS company purchased by Akamai, but that doesnt appear to be the reason why.
.homeand.homenetwere proposed, but this is from the mailing list:- we cannot be sure that using .home is consistent with the existing (ab)use
- ICANN is in receipt of about a dozen applications for “.home”, and some of those applicants no doubt have deeper pockets than the IETF does should they decide to litigate
…ietf.org/…/PWl6CANKKAeeMs1kgBP5YPtiCWg/
So, corporate fear.
lars@lemmy.sdf.org 3 months ago
But
home.arpa’s top-level domain is.arpa?fmstrat@lemmy.nowsci.com 3 months ago
I’m not sure I follow the question. All of the TLD
*.arpais not reserved for private use, only*.home.arpa. So all your internal services are required to be a sub domain.
fmstrat@lemmy.nowsci.com 3 months ago
I just use openssl"s built in management. I have scripts that set it up and generate a
.landomain, and instructions for adding it to clients. I could make a repo and writeup if you would like?As the other commenter pointed out,
.lanis not officially sanctioned for local use, but it is not used publicly and is a common choice. However you could use whatever you want.