1 |
On 2022-01-15 10:33+0000 Peter Humphrey <peter@××××××××××××.uk> wrote: |
2 |
|
3 |
> Hello list, |
4 |
> |
5 |
> Rich F said recently, "I'd avoid using the .local TLD due to RFC |
6 |
> 6762." |
7 |
> |
8 |
> That brings me back to a thorny problem: what should I call my local |
9 |
> network? It used to be .prhnet, but then a program I tried a few |
10 |
> years ago insisted on a two-component name, so I changed it to |
11 |
> .prhnet.local. |
12 |
> |
13 |
> Now I've read that RFC - well, Appendix G to it - and I'm scratching |
14 |
> my head. I suppose it's possible that someone may want to connect an |
15 |
> Apple device to my network, so perhaps I should clear the way for |
16 |
> that eventuality. |
17 |
> |
18 |
> So, what TLD should I use? Should I use .home, or just go back to |
19 |
> .prhnet? It isn't going to be visible to the Big Bad World, so does |
20 |
> it even matter? |
21 |
> |
22 |
|
23 |
ICANN rejected .home as a TLD¹ because of name collision issues in |
24 |
private networks, so that should be fine. |
25 |
|
26 |
Another solution would be to register an inexpensive domain name and use |
27 |
that. 😊 |
28 |
|
29 |
Kind regards, tastytea |
30 |
|
31 |
¹ <https://en.wikipedia.org/wiki/.home> |
32 |
|
33 |
-- |
34 |
Get my PGP key with `gpg --locate-keys tastytea@××××××××.de` or at |
35 |
<https://tastytea.de/tastytea.asc>. |