On Sat 15 Jan 2022 11:53:58 GMT, tastytea wrote: > On 2022-01-15 10:33+0000 Peter Humphrey <pe...@prh.myzen.co.uk> wrote: > > > Hello list, > > > > Rich F said recently, "I'd avoid using the .local TLD due to RFC > > 6762." > > > > That brings me back to a thorny problem: what should I call my local > > network? It used to be .prhnet, but then a program I tried a few > > years ago insisted on a two-component name, so I changed it to > > .prhnet.local. > > > > Now I've read that RFC - well, Appendix G to it - and I'm scratching > > my head. I suppose it's possible that someone may want to connect an > > Apple device to my network, so perhaps I should clear the way for > > that eventuality. > > > > So, what TLD should I use? Should I use .home, or just go back to > > .prhnet? It isn't going to be visible to the Big Bad World, so does > > it even matter? > > > > ICANN rejected .home as a TLD¹ because of name collision issues in > private networks, so that should be fine. > > Another solution would be to register an inexpensive domain name and use > that. 😊 > > Kind regards, tastytea > > ¹ <https://en.wikipedia.org/wiki/.home>
home.arpa has to be used instead -- Alarig
