1 |
On Sat, Jan 15, 2022 at 5:57 AM William Kenworthy <billk@×××××××××.au> wrote: |
2 |
> |
3 |
> On 15/1/22 18:33, Peter Humphrey wrote: |
4 |
> > Hello list, |
5 |
> > |
6 |
> > Rich F said recently, "I'd avoid using the .local TLD due to RFC 6762." |
7 |
> > |
8 |
> > That brings me back to a thorny problem: what should I call my local network? |
9 |
> > It used to be .prhnet, but then a program I tried a few years ago insisted on |
10 |
> > a two-component name, so I changed it to .prhnet.local. |
11 |
> > |
12 |
> > Now I've read that RFC - well, Appendix G to it - and I'm scratching my head. |
13 |
> > I suppose it's possible that someone may want to connect an Apple device to my |
14 |
> > network, so perhaps I should clear the way for that eventuality. |
15 |
> > |
16 |
> > So, what TLD should I use? Should I use .home, or just go back to .prhnet? It |
17 |
> > isn't going to be visible to the Big Bad World, so does it even matter? |
18 |
> > |
19 |
> Ive been using "localdomain" for years without any obvious problems. |
20 |
> .local is not just apple but can be used by other things too (e.g., |
21 |
> homeassistant uses it for device discovery, creating an extensive |
22 |
> ecosystem in the process. No apple devices in sight :) |
23 |
|
24 |
Just about everything supports mDNS, including Gentoo: |
25 |
https://wiki.gentoo.org/wiki/Avahi |
26 |
|
27 |
(Most desktop-oriented distros enable it by default.) |
28 |
|
29 |
You might want to look into whether it solves your problems |
30 |
out-of-the-box without the need to run internal DNS. The latter still |
31 |
has certain advantages, but mDNS obviously benefits from simplicity. |
32 |
|
33 |
-- |
34 |
Rich |