On Sat, Jan 15, 2022 at 5:57 AM William Kenworthy <bi...@iinet.net.au> wrote: > > On 15/1/22 18:33, Peter Humphrey 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? > > > Ive been using "localdomain" for years without any obvious problems. > .local is not just apple but can be used by other things too (e.g., > homeassistant uses it for device discovery, creating an extensive > ecosystem in the process. No apple devices in sight :)
Just about everything supports mDNS, including Gentoo: https://wiki.gentoo.org/wiki/Avahi (Most desktop-oriented distros enable it by default.) You might want to look into whether it solves your problems out-of-the-box without the need to run internal DNS. The latter still has certain advantages, but mDNS obviously benefits from simplicity. -- Rich
